Agent skill

Type Coercion

by thedaviddias in thedaviddias/Front-End-Checklist

A skill your agent uses when reviewing scripts, client components, bundles, or runtime behavior related to Avoid implicit type coercion.

MITAuto-check passed

Install Type Coercion

skills CLI
$ npx skills add thedaviddias/Front-End-Checklist --skill type-coercion -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install thedaviddias/Front-End-Checklist type-coercion --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/type-coercion .claude/skills/type-coercion && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
type-coercion
GitHub stars
74k
Token cost
~493 tokens
SKILL.md length
201 words
Files
2 (incl. references)
Skills in repo
390
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when reviewing scripts, client components, bundles, or runtime behavior related to Avoid implicit type coercion.

  • Reviewing scripts
  • SKILL.md covers Quick Reference, Check, Fix and Explain, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Client components

What it does

Type Coercion is an agent skill from thedaviddias/Front-End-Checklist. Use when reviewing scripts, client components, bundles, or runtime behavior related to Avoid implicit type coercion. Inspect both source code and the browser execution path so fixes target the real bottleneck or bug.

Its SKILL.md is about 490 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/rule.md`).

The repository describes itself as: 🗂 The essential checklist for modern web development, for humans and AI agents. The licence is MIT.

When your agent uses it

  • Reviewing scripts
  • Client components
  • Runtime behavior related to Avoid implicit type coercion

Example prompts

  • “/type-coercion”

What it can do on your machine

Read from SKILL.md and the folder at commit e8d14d0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • frontendchecklist.io

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Type Coercion loads about 493 tokens when it runs, and up to ~1.5k if it reads all its reference files. Until then it costs about 58 tokens; SKILL.md has 201 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~58
When it runs · the whole SKILL.md, loaded when a task matches
~493
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from thedaviddias/Front-End-Checklist at commit e8d14d0, republished under its MIT licence (© thedaviddias). 201 words, ~493 tokens.

Download SKILL.mdSave it as .claude/skills/type-coercion/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
type-coercion
description
Use when reviewing scripts, client components, bundles, or runtime behavior related to Avoid implicit type coercion. Inspect both source code and the browser execution path so fixes target the real bottleneck or bug.
metadata.category
javascript
metadata.priority
medium
metadata.difficulty
beginner
metadata.estimatedTime
15
metadata.source
frontendchecklist.io
metadata.url
https://frontendchecklist.io/rules/javascript/type-coercion

Avoid implicit type coercion

JavaScript's implicit type coercion produces results that look like bugs to anyone who doesn't know the exact coercion rules. == comparisons with mixed types silently convert values in ways that fail to catch genuine errors. Explicit conversions make code intent clear and catch real type mismatches at the point where they occur.

Quick Reference

  • Always use === and !== instead of == and !=
  • Convert types explicitly with Number(), String(), Boolean(), parseInt()
  • Be careful with + operator — it concatenates strings but adds numbers
  • Use Array.isArray() instead of typeof for array checks

Check

Find all uses of == and != (non-strict equality) in this file. Also look for implicit type conversions from + operator and other coercion traps.

Fix

Replace all == with === and != with !==. Add explicit type conversions where mixed types are intentionally compared.

Explain

Explain JavaScript's implicit type coercion rules, why == is problematic, and how to write safe type comparisons.

Code Review

Review scripts, client components, and browser execution paths related to Avoid implicit type coercion. Flag exact imports, event handlers, runtime side effects, or blocking operations that violate the rule, and state how the change should be verified in the browser.


For full implementation details, code examples, and framework-specific guidance, see references/rule.md.

Rule page: https://frontendchecklist.io/rules/javascript/type-coercion

© thedaviddias, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/type-coercion of thedaviddias/Front-End-Checklist.

  • SKILL.md
  • references/rule.md

Open the folder on GitHubat commit e8d14d0

Compare with similar skills

Type Coercion next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Type Coercion compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Type Coercion this skillthedaviddias/Front-End-Checklist74k—~493Automated safety check: PassMIT
Triage Support Bundlenetdata/netdata81k—~2.7kAutomated safety check: PassGPL-3.0
Analyzing Backend BundleTriliumNext/Trilium38k—~2.6kAutomated safety check: PassAGPL-3.0
Next Bundle Optimizervercel/next.js143k—~2.4kAutomated safety check: PassMIT
Optimize Bundle Sizeelastic/kibana21k—~794Automated safety check: PassCustom licence
Production Bundle Auditkeybase/client9.3k—~620Automated safety check: PassBSD-3-Clause

Similar skills

  • Triage Support Bundle

    netdata/netdata

    Investigate a Netdata support bundle offline - the archive netdata-support-bundle produces - to explain one host's alerts, missing data, collector failures, crashes, high CPU or memory, streaming…

    81k GitHub stars~2.7k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Analyzing Backend Bundle

    TriliumNext/Trilium

    A skill your agent uses when analyzing the server/desktop backend bundle — "what does the server load at startup?", "is <dependency lazy on the backend?", "why is <package in the startup set?", "how…

    38k GitHub stars~2.6k tokensUpdated today
    Knowledge ManagementAuto-check passed
  • Next Bundle Optimizer

    vercel/next.js

    Official

    Audit and reduce Next.js browser initial-load work. An agent skill from vercel/next.js.

    143k GitHub stars~2.4k tokensUpdated today
    Auto-check passed
  • Optimize Bundle Size

    elastic/kibana

    Official

    Reduce plugin page load bundle size and avoid unnecessary increases in packages/kbn-rspack-optimizer/limits.yml.

    21k GitHub stars~794 tokensUpdated today
    Frontend & DesignAuto-check passed
  • Builds the desktop Vite and iOS or Android Metro production bundles and checks them for tree-shaking problems, such as mobile-only modules leaking into the desktop build.

    9.3k GitHub stars~620 tokensUpdated today
    Frontend & DesignAuto-check passed
  • Create Paperclip Bundled Skill

    paperclipai/paperclip

    Turn an idea, tweet, or task into a skill in the Paperclip skills catalog (packages/skills-catalog).

    99k GitHub stars~2.7k tokensUpdated today
    Writing & ContentAuto-check passed

More from thedaviddias/Front-End-Checklist

All 390 skills in this repo
  • Content Dates Audit

    thedaviddias/Front-End-Checklist

    Audits article and blog pages for visible publish dates, Article JSON-LD with datePublished and dateModified, and Open Graph time tags, then fixes what is missing.

    74k GitHub stars~691 tokensUpdated 3 days ago
    Auto-check passed
  • FAQPage Schema Markup

    thedaviddias/Front-End-Checklist

    Adds, checks and fixes FAQPage JSON-LD on pages with visible question-and-answer sections so it matches what readers see and can qualify for rich results.

    74k GitHub stars~774 tokensUpdated 3 days ago
    Auto-check passed
  • Favicon Audit and Setup

    thedaviddias/Front-End-Checklist

    Checks that a site's favicon is linked, reachable and large enough for Google search results, and sets up ICO, SVG and Apple touch icon files when they are missing.

    74k GitHub stars~731 tokensUpdated 3 days ago
    Auto-check passed
  • Content Freshness Signals

    thedaviddias/Front-End-Checklist

    Audits article pages for freshness signals, covering the Last-Modified header, Article JSON-LD dateModified and a visible last-updated date, and fixes mismatches.

    74k GitHub stars~741 tokensUpdated 3 days ago
    Auto-check passed
  • Geo Meta Tags Audit

    thedaviddias/Front-End-Checklist

    Audits and fixes geo.region, geo.placename and geo.position meta tags on regional pages, noting where they help (Bing) and where they do not (Google).

    74k GitHub stars~763 tokensUpdated 3 days ago
    Auto-check passed
  • Improve a Front-End Checklist Rule

    thedaviddias/Front-End-Checklist

    Scores and rewrites a Front-End Checklist rule MDX file against a scored quality rubric, replacing generic stub prompts with specific, actionable ones.

    74k GitHub stars~1.3k tokensUpdated 3 days ago
    Auto-check passed

Questions about Type Coercion

What does Type Coercion do?

A skill your agent uses when reviewing scripts, client components, bundles, or runtime behavior related to Avoid implicit type coercion. Type Coercion is an agent skill from thedaviddias/Front-End-Checklist. Use when reviewing scripts, client components, bundles, or runtime behavior related to Avoid implicit type coercion.

When should I use Type Coercion?

Type Coercion fits situations like: reviewing scripts; client components; runtime behavior related to Avoid implicit type coercion.

How do I install Type Coercion in Claude Code?

Run `npx skills add thedaviddias/Front-End-Checklist --skill type-coercion -a claude-code`. Or copy the skill folder (skills/type-coercion in thedaviddias/Front-End-Checklist) into .claude/skills/type-coercion in your project. Claude Code loads it when a task matches its description.

How do I install Type Coercion in Codex?

Run `npx skills add thedaviddias/Front-End-Checklist --skill type-coercion -a codex`. Or copy the skill folder (skills/type-coercion in thedaviddias/Front-End-Checklist) into .agents/skills/type-coercion in your project. Codex loads it when a task matches its description.

Can I use Type Coercion in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add thedaviddias/Front-End-Checklist --skill type-coercion -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/type-coercion, .gemini/skills/type-coercion, .github/skills/type-coercion and .opencode/skills/type-coercion in your project.

What does Type Coercion need to run?

SKILL.md names no scripts, command-line tools or credentials: Type Coercion is instructions for the agent only.

Does Type Coercion access the network?

SKILL.md names 1 domain. As links in the text: frontendchecklist.io. This is read from the text; nothing was executed.

Is Type Coercion safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Type Coercion use?

Type Coercion is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Type Coercion use?

About 493 tokens (SKILL.md is roughly 2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 969 tokens, read only when the agent opens those files.

What are the alternatives to Type Coercion?

Skills that share tags, products or a category with Type Coercion: Triage Support Bundle (netdata/netdata, 81k stars), Analyzing Backend Bundle (TriliumNext/Trilium, 38k stars), Next Bundle Optimizer (vercel/next.js, 143k stars) and Optimize Bundle Size (elastic/kibana, 21k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Type Coercion?

thedaviddias (a GitHub user) maintains it in thedaviddias/Front-End-Checklist, which has 74,421 GitHub stars. The repository holds 390 skills in this directory. The repository was last updated on October 6, 2026.

Source: thedaviddias/Front-End-Checklist on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.