SkillKit is a package manager for AI coding-agent skills that installs skills from many sources and translates them between the different formats used by coding agents. It helps developers share skills across agents such as Claude Code, Cursor, Copilot, and Codex.
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 rohitg00/skillkit --skill task-decompositiongit clone --depth 1 https://github.com/rohitg00/skillkitWrote 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/rohitg00/skillkit/task-decomposition)<a href="https://agentmods.dev/skills/rohitg00/skillkit/task-decomposition"><img src="https://agentmods.dev/badge/skills/rohitg00/skillkit/task-decomposition/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/rohitg00/skillkit/task-decomposition"><img src="https://agentmods.dev/badge/skills/rohitg00/skillkit/task-decomposition.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00108 | $0.01158 |
| Opus 5.5 | $0.00043 | $0.00463 |
| Sonnet 5.5 | $0.00022 | $0.00232 |
| Haiku 4.5 | $0.00011 | $0.00116 |
Grade A, and why
task-decomposition 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 1mo 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Decomposition
You are breaking down a complex task into smaller, atomic units. Each unit should be independently completable and verifiable.
Core Principle
If a task feels too big, it is too big. Break it down until each piece is obvious.
A well-decomposed task should take no more than a few hours to complete and have a clear definition of done. Aim for tasks that are small, independent, testable, and clearly scoped.
Decomposition Techniques
1. Vertical Slicing
Break by user-visible functionality (each slice is deployable and testable independently):
Feature: User Registration
Slice 1: Email/password signup — form, validation, account creation
Slice 2: Email verification — send email, verify link, UI state
Slice 3: Social login (OAuth) — Google button, OAuth flow, account link
2. Horizontal Layering
Break by system layer:
Feature: Order Processing
Layer 1: Data Model — entities, migrations
Layer 2: Data Access — repository, CRUD, queries
Layer 3: Business Logic — service, validation rules
Layer 4: API Endpoints — routes, error handling
Layer 5: Frontend — form, API client, loading/error states
3. Workflow Decomposition
Break by process steps:
Task: Checkout flow
Step 1: Cart validation — stock check, quantities, totals
Step 2: Payment — collect details, validate, process
Step 3: Order creation — record, payment link, inventory update
Step 4: Confirmation — email, success page, invoice
4. Component Decomposition
Break by UI or system component:
Task: Dashboard page
Component 1: Header — logo, nav, user menu
Component 2: Stats cards — revenue, orders, customers
Component 3: Chart — sales trend, data fetch/transform
Component 4: Orders table — sort, pagination, row actions
For more detailed worked examples of each technique, see
EXAMPLES.md.
Task Template
For each decomposed task, define:
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.
- 1mo ago First seen · 172 lines · 108 tokens per session scan A 13592306938b
task-decomposition is a skill published in the GitHub repository rohitg00/skillkit (1,555 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 108 tokens to every session and 1,158 once invoked, about $0.0004 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
user-research-cookiy
End-to-end user research assistant — qualitative and quantitative. Use this skill whenever the user mentions user research, user interviews, discussion guides, interview guides, research plans, qualitative research, quantitative research, user surveys, survey design, usability studies, participant recruitment…
Agent Browser Automation
Fast Rust-based headless browser automation CLI with Node.js fallback for AI agents, featuring navigation, clicking, typing, snapshots, and structured commands optimized for agent workflows.
best-practices
Transforms vague prompts into optimized Claude Code prompts. Adds verification, specific context, constraints, and proper phasing. Invoke with /best-practices.
code-documentation
Writing effective code documentation - API docs, README files, inline comments, and technical guides. Use for documenting codebases, APIs, or writing developer guides.
curate-a-team-library
Use when building a managed team skills library for a real stack. Map work to shelves, browse before curating, write meaningful whyHere notes, and create a starter pack once the first pass is solid.
migrate-skills-between-libraries
Use when moving skills between library workspaces or upgrading from a personal library to a team library. Export from one workspace, import into another.