write-a-skill
Skill16 starsChanged 6 months agoMITView on GitHub
Output: "Creating pdf-extraction skill. Description: Extract text and tables from PDF files. Use when working with PDF files or when user mentions forms or document extraction. Structure: - skill.md: Core instructions. - scripts/parse.py: Python helper for PDF parsing."
122 other projects use a version of this.
Adopted by
Most recently taken up by
- robotostudio/hotrodtheir own version, first seen Nov 8, 2026
- aditya-vermax/skillstheir own version, first seen Nov 8, 2026
- domengabrovsek/agent-configtheir own version, first seen Nov 8, 2026
- domengabrovsek/claudetheir own version, first seen Nov 8, 2026
- darkweb19/skillstheir own version, first seen Nov 8, 2026
- matheus3006/my-claude-skillstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use ubiquitous-language, prd-to-plan and 4 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
kennethkeimSkillubiquitous-language
Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "DDD".
Also in 20 projects that use this
HK-hubSkillprd-to-plan
Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in ./plans/. Use when user wants to break down a PRD, create an implementation plan, plan phases from a PRD, or mentions "tracer bullets".
Also in 7 projects that use this
semtexfromuaSkillhow-to
Курс typing-уроків по існуючому проекту — «як написати його з нуля»: аналіз → план у .practicum/course.md → покрокова генерація уроків. Використовуй для команди /vibe-typing:how-to.
Also in 3 projects that use this
GoogleSkillsetup-matt-pocock-skills
Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
Also in 33 projects that use this
ShopifySkilltriage-issue
Triage a GitHub issue — classify priority (P0/P1/P2), search for duplicates, and apply labels.
Also in 7 projects that use this
GoogleSkillimprove-codebase-architecture
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
Also in 59 projects that use this
Other versions122 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 122
- sanity-io/sanity★ 6.4ksame name
- victorgarciaesgi/regle★ 508same name
- amazingloft999-droid/mattpocock-skills★ 422same name
- InditexTech/weavejs★ 266same name
- ayoubben18/ab-method★ 192same name
- yamcodes/arkenv★ 151same name
- alex-on-ai/WebReaper★ 149same name
- aurorasoft2/Matt_Pocock_Skills★ 133same name
- better-stack-ai/better-stack★ 79same name
- VisualxIntelligence/mattpocok-skills★ 55same name
112 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository44 other files it gives its agents.
- accessibility-auditSkill
- api-designSkill
- architecture-designSkill
- ax-extract-workflowSkill
- blockchain-smart-contractsSkill
- cavemanSkill
- cloud-architectureSkill
- code-explanationSkill
- code-generationSkill
- code-migrationSkill
- code-reviewSkill
- css-animationsSkill
- database-designSkill
- data-science-edaSkill
- debuggingSkill
- devops-pipelineSkill
- diagnoseSkill
- documentationSkill
- game-mechanicsSkill
- graphql-schemaSkill
- grill-meSkill
- grill-with-docsSkill
- i18n-l10nSkill
- linux-sysadminSkill
- onboardingSkill
- performance-optimizationSkill
- prompt-engineeringSkill
- prototypeSkill
- refactoringSkill
- regex-wizardSkill
- security-auditSkill
- seo-optimizationSkill
- skillsSkill
- tddSkill
- _templateSkill
- testingSkill
- to-issuesSkill
- to-prdSkill
- tree-ring-memorySkill
- triageSkill
- ux-ui-reviewSkill
- web-scrapingSkill
- x-twitter-scraperSkill
- zoom-outSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 4 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 118 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 7
Create new Claude skills with proper structure, progressive disclosure, and bundled resources to expand an agent's capabilities.
- Very specific: line 11
Concise instructions: Keep the main skill.md focused.
- Distinctive: line 12
Deterministic Helpers: Add utility scripts for operations that are repetitive or need strict validation.
- Distinctive: line 13
Third Person: Write descriptions in the third person for the agent's system prompt.
- Distinctive: line 16
Gather: Ask about the domain, use cases, and needed scripts.
- Very specific: line 17
Draft: Create the skill.md and any supporting READMEs or scripts.
“Common” is measured: kept by at least 6 in 10 of the 118 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Skill: Write a Skill
Role
You are a Prompt Engineer and Agent Workflow Expert.
Objective
Create new Claude skills with proper structure, progressive disclosure, and bundled resources to expand an agent's capabilities.
Constraints
- Trigger-Focused: The skill description must clearly state when and why to use it ("Use when...").
- Concise instructions: Keep the main
skill.mdfocused. Use supplementary files for heavy documentation. - Deterministic Helpers: Add utility scripts for operations that are repetitive or need strict validation.
- Third Person: Write descriptions in the third person for the agent's system prompt.
Process
- Gather: Ask about the domain, use cases, and needed scripts.
- Draft: Create the
skill.mdand any supporting READMEs or scripts. - Review: Present the draft to the user for clarity and coverage check.
- Refine: Iterate based on feedback until the skill is "AI-ready."
Output Format
- Skill Structure: A tree view of the new skill directory.
- Skill.md Content: The core instructions and triggers.
- Utility Scripts: (Optional) Code for helper scripts.
Examples
Example 1: New PDF Skill
Input: "I want a skill to help me extract data from PDFs."
Output:
"Creating pdf-extraction skill.
Description: Extract text and tables from PDF files. Use when working with PDF files or when user mentions forms or document extraction.
Structure:
skill.md: Core instructions.scripts/parse.py: Python helper for PDF parsing."
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

