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 gleanwork/cursor-plugins --skill skill-creation-guidegit clone --depth 1 https://github.com/gleanwork/cursor-pluginsWrote 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/gleanwork/cursor-plugins/skill-creation-guide)<a href="https://agentmods.dev/skills/gleanwork/cursor-plugins/skill-creation-guide"><img src="https://agentmods.dev/badge/skills/gleanwork/cursor-plugins/skill-creation-guide/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/gleanwork/cursor-plugins/skill-creation-guide"><img src="https://agentmods.dev/badge/skills/gleanwork/cursor-plugins/skill-creation-guide.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.00136 | $0.01169 |
| Opus 5.5 | $0.00054 | $0.00468 |
| Sonnet 5.5 | $0.00027 | $0.00234 |
| Haiku 4.5 | $0.00014 | $0.00117 |
Grade A, and why
skill-creation-guide 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.
This is a copy
100% identical to skill-creation-guide — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Creation Guide
Help the user author effective agent skills — single SKILL.md files (in the
open Agent Skills format) that auto-trigger by context and provide specialized
guidance. The format is shared across hosts (Claude Code, Cursor, and others);
only the install location differs.
This skill covers three things: deciding whether a skill is worth creating, discovering candidates from the user's work, and generating a well-formed skill.
BE SKEPTICAL
Not every idea makes a good skill. Evaluate before creating:
Recurrence — Will this be used repeatedly?
- ✅ Weekly or more → create
- ⚠️ Monthly → reconsider, may not be worth it
- ❌ One-time → skip
Automation — Can it actually be automated?
- ✅ Clear, repeatable process → create
- ⚠️ Needs significant judgment each time → reconsider
- ❌ Too context-dependent, each case unique → skip
Value — Is the cumulative time saved significant?
- ✅ Meaningful savings per use → create
- ❌ Slower to invoke than doing manually → skip
Duplication — Does it already exist?
- ✅ Novel, unaddressed need → create
- ⚠️ Similar to an existing skill → enhance that instead
- ❌ Already covered → skip
Don't create skills for one-time events, tasks that differ fundamentally each time, sub-30-second manual tasks, or things the user will forget exist.
Workflow A — Discover opportunities
When the user asks what they should automate, analyze their work patterns first.
Requires the Glean MCP tools. If they aren't visible, ask the user to set up
Glean by prompting the harness (for example, Set up Glean for me).
- Gather context with Glean:
memory(roles, responsibilities, active projects),user_activity(past ~2 weeks), andsearchfor process docs ("runbook OR checklist OR process owner:me"). - Spawn the
work-pattern-analyzeragent to identify repeated queries, frequent contexts, workflow sequences, and manual processes — and to vet each candidate against the recurrence/value tests above. - Present vetted recommendations grouped by cumulative value, and show the rejected candidates with reasons. A few high-quality candidates beat many weak ones — "no automatable patterns" is a valid outcome.
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 · 120 lines · 136 tokens per session scan A 5722a8039076
skill-creation-guide is a skill published in the GitHub repository gleanwork/cursor-plugins (4 stars, last pushed 17d ago), licensed MIT. It adds 136 tokens to every session and 1,169 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to skill-creation-guide, differing in 0 lines, and is treated as a copy.
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…