agentleFS
ntaffziintaffzii/Skill-Agents/skills/research/github-skill-research/SKILL.md

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.

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
  1. Distinctive:

    If the target is unclear, make a narrow useful assumption and state it.

    line 14
  2. Distinctive:

    Prefer official documentation and maintained repositories over generic blog advice.

    line 18
  3. Distinctive:

    Call out duplication, overbroad skills, stale instructions, and missing validation.

    line 28
  4. Distinctive:

    Keep templates short enough to install or edit immediately.

    line 33
  5. Distinctive:

    Do not summarize sources without links or file paths.

    line 57
  6. Distinctive:

    Do not copy a skill verbatim unless the user asks.

    line 58
  7. Very specific:

    Keep trigger logic in YAML description.

    line 59
  8. Distinctive:

    Prefer workflows with verification over advice-only prompts.

    line 60

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

GitHub Skill Research

Research reusable AI-agent skill patterns from real repositories and primary documentation.

Workflow

  1. 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.
  2. 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-skills as 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.
  3. 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.
  4. 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.
  5. 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 Items

Rules

  • 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.