Claude With Skills is a progressive course that teaches developers to create reusable, portable Agent Skills for Claude Code, from basic SKILL.md files to advanced automation and plugin packaging. It is intended for developers who want repeatable instructions and workflows instead of repeatedly pasting the same guidance. The catalogue contains the course's skills, agents, and instruction.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add davila7/claude-with-skills --skill migrate-componentgit clone --depth 1 https://github.com/davila7/claude-with-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/davila7/claude-with-skills/migrate-component)<a href="https://agentmods.dev/skills/davila7/claude-with-skills/migrate-component"><img src="https://agentmods.dev/badge/skills/davila7/claude-with-skills/migrate-component/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/davila7/claude-with-skills/migrate-component"><img src="https://agentmods.dev/badge/skills/davila7/claude-with-skills/migrate-component.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00020 | $0.00618 |
| Opus 5.5 | $0.00008 | $0.00247 |
| Sonnet 5.5 | $0.00004 | $0.00124 |
| Haiku 4.5 | $0.00002 | $0.00062 |
Grade A, and why
migrate-component scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migrate component
Migrate the $0 component from $1 to $2.
Step 1: Read the current implementation
Find and read the current $0 component file. Search for it:
- In
src/components/,components/,app/components/, or similar common locations - Using
grep -r "$0" --include="*.$1*" -lif the framework extension is known (e.g.,.vue,.jsx)
Read all files that make up the component:
- The main component file
- Any associated style files (
.css,.scss,.module.css) - Any associated test files (
*.test.*,*.spec.*)
If you cannot find the component, stop and ask the user for the file path.
Step 2: Understand props, state, and behavior
Before writing any code, document:
- All props the component accepts (name, type, default value, whether required)
- All internal state (what it tracks and how it changes)
- All events the component emits or callbacks it invokes
- Side effects (data fetching, subscriptions, DOM manipulation)
- The rendered structure (what it produces visually or structurally)
This documentation becomes the specification the new implementation must satisfy.
Step 3: Write the equivalent in $2
Write the $0 component in $2, matching the same public API:
- Same prop names and types
- Same event names and payloads
- Same rendered structure (or nearest equivalent in $2)
- Same behavior for all documented state transitions
Use idiomatic $2 patterns. Do not transliterate $1 patterns directly into $2 if $2 has a better way to express the same thing.
Step 4: Update tests
Rewrite any tests associated with the original component to use $2 testing conventions:
- Update imports to point to the new component file
- Update any framework-specific test utilities (e.g.,
mountfrom $1 to the $2 equivalent) - Preserve all test cases — every behavior tested in $1 must be tested in $2
Step 5: Report what changed and what needs manual review
Produce a brief report:
Changed:
- List of files created or modified
Preserved:
- Confirmation that all props, events, and behaviors have equivalents
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2mo ago First seen · 70 lines · 20 tokens per session scan A bd0431127792
migrate-component is a skill published in the GitHub repository davila7/claude-with-skills (13 stars, last pushed 5mo ago), licensed MIT. It adds 20 tokens to every session and 618 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…