github-skill-research
Skill4 starsChanged 2 months agoMITView on GitHub
Research real AI-agent skill repositories, official docs, prompt libraries, SKILL.md patterns, AGENTS.md or CLAUDE.md conventions, and reusable workflow prompts. Use when creating, improving, auditing, comparing, templating, or monitoring AI agent skills and workflow repositories.
In this repository58 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/project-docs-prep/templates/AGENTS.mdAGENTS.md
- skills/project-docs-prep/templates/CLAUDE.mdCLAUDE.md
- deep-planningSkill
- deep-planningSkill
- deprecatedSkill
- architecture-reviewSkill
- code-reviewSkill
- diagnoseSkill
- tddSkill
- ui-design-engineeringSkill
- ux-ui-design-assessmentSkill
- in-progressSkill
- mcp-tool-managementSkill
- skill-managementSkill
- obsidian-canvasSkill
- obsidian-markdownSkill
- obsidian-notion-bridgeSkill
- obsidian-vault-workflowSkill
- boomz-preferencesSkill
- personal-agent-workflowSkill
- personalSkill
- automation-designSkill
- grill-with-docsSkill
- handoffSkill
- inbox-meeting-triageSkill
- markdown-reportSkill
- prompt-improvementSkill
- project-docs-prepSkill
- claim-citation-checkSkill
- daily-news-reportSkill
- project-discoverySkill
- repo-tourSkill
- research-methodologySkill
- seo-website-evaluatorSkill
- thaiSkill
- thai-addressSkill
- thai-customer-serviceSkill
- thai-date-formatSkill
- thai-festival-cardSkill
- thai-government-formSkill
- thai-id-validateSkill
- thai-invoiceSkill
- thai-pdpaSkill
- thai-resumeSkill
- thai-social-captionSkill
- thai-text-processingSkill
- thai-translateSkill
- backtest-expertSkill
- dividend-value-screenerSkill
- drawdown-circuit-breakerSkill
- exposure-coachSkill
- market-breadth-analyzerSkill
- portfolio-managerSkill
- position-sizerSkill
- tradingSkill
- trader-memory-coreSkill
- uptrend-analyzerSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
If the target is unclear, make a narrow useful assumption and state it.
- Distinctive: line 18
Prefer official documentation and maintained repositories over generic blog advice.
- Distinctive: line 28
Call out duplication, overbroad skills, stale instructions, and missing validation.
- Distinctive: line 33
Keep templates short enough to install or edit immediately.
- Distinctive: line 57
Do not summarize sources without links or file paths.
- Distinctive: line 58
Do not copy a skill verbatim unless the user asks.
- Very specific: line 59
Keep trigger logic in YAML description.
- Distinctive: line 60
Prefer workflows with verification over advice-only prompts.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
GitHub Skill Research
Research reusable AI-agent skill patterns from real repositories and primary documentation.
Workflow
- Define the research target
- Identify whether the user wants structure, trigger logic, workflow design, operating rules, examples, portability, or repository organization.
- If the target is unclear, make a narrow useful assumption and state it.
- Search sources
- Prioritize real repositories with
SKILL.md,AGENTS.md,CLAUDE.md, prompt libraries, workflow playbooks, or MCP/tooling examples. - Prefer official documentation and maintained repositories over generic blog advice.
- Include
thananon/9arm-skillsas a useful comparison point when evaluating concise skill structure. - See research-methodology for tiering sources (repo itself vs. a blog post about the repo) and tracking which candidates were actually checked vs. skipped.
- Prioritize real repositories with
- Analyze examples
- Extract frontmatter style, trigger descriptions, workflow steps, output formats, safety rules, bundled resources, and repo layout.
- Identify whether each pattern is portable across agents or tied to one tool.
- Compare against the user's repo
- Mark patterns to copy, adapt, skip, or keep private.
- Call out duplication, overbroad skills, stale instructions, and missing validation.
- Produce recommendations
- Respond in the user's language.
- Include links or local file paths.
- Keep templates short enough to install or edit immediately.
Output Format
# AI Agent Skill Research
## Summary
## Useful Sources
## Patterns To Copy
## Patterns To Adapt
## Anti-patterns To Avoid
## Suggested Skill Template
## Action ItemsRules
- Do not summarize sources without links or file paths.
- Do not copy a skill verbatim unless the user asks.
- Keep trigger logic in YAML
description. - Prefer workflows with verification over advice-only prompts.
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.

