agentleFS
ItalyPaleAleItalyPaleAle/skills/go-package-skill-creator/SKILL.md

go-package-skill-creator

Skill1 starsChanged 9 months agoMITView on GitHub

Create skills for Go packages by fetching documentation from pkg.go.dev and generating structured SKILL.md files with usage patterns, examples, and best practices. Use when the user wants to create a skill for a specific Go package (e.g., "create a skill for github.com/lestrrat-go/jwx/v3") or needs to document how to use a Go library.

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 8 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the package has multiple subpackages, fetch the most relevant ones

    line 20
  2. Very specific:

    Name: Use go- and the last segment of import path (e.g., jwx from github.com/lestrrat-go/jwx/v3)

    line 28
  3. Very specific:

    If name is too generic (like http or json), prepend with package scope (e.g., go-fasthttp)

    line 29
  4. Distinctive:

    When to trigger: "Use when working with [domain], [specific task], or when the user mentions [package name]"

    line 33
  5. Distinctive:

    Keep under 500 lines if possible

    line 44
  6. Very specific:

    Use Write tool to create SKILL.md

    line 50
  7. Distinctive:

    Create any necessary reference files

    line 51
  8. Distinctive:

    No README.md or auxiliary documentation

    line 52
  9. Distinctive:

    Check that description is comprehensive and includes triggers

    line 56
  10. Distinctive:

    Ensure examples are runnable

    line 57
  11. Distinctive:

    Verify references are properly linked if used

    line 58

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Go Package Skill Creator

Generate skills that teach how to use specific Go packages.

Workflow

  1. Gather information:
    • Package import path (e.g., github.com/lestrrat-go/jwx/v3)
    • Additional examples or use cases (optional)
    • Any specific aspects to emphasize (optional)
  2. Fetch documentation:
    • Get package documentation from https://pkg.go.dev/<import-path>
    • Extract: package overview, main types, key functions, and code examples
    • If the package has multiple subpackages, fetch the most relevant ones
  3. Analyze package complexity:
    • Simple (single purpose, <10 key functions): Focus on core usage pattern with 1-2 examples
    • Medium (multiple types, 10-30 functions): Include common patterns and error handling
    • Complex (framework-like, >30 functions): Split into sections, consider references/ for advanced topics
  4. Derive skill identity:
    • Name: Use go- and the last segment of import path (e.g., jwx from github.com/lestrrat-go/jwx/v3)
      • If name is too generic (like http or json), prepend with package scope (e.g., go-fasthttp)
    • Description: Include:
      • What the package does (1 sentence)
      • Primary use cases (2-3 bullet points)
      • When to trigger: "Use when working with [domain], [specific task], or when the user mentions [package name]"
  5. Create skill structure:
    <package-name>/
    ├── SKILL.md
    └── references/        (optional, only if complex)
        └── advanced.md
  6. Write SKILL.md following the template in references/skill-template.md:
    • Keep under 500 lines if possible
    • Focus on practical patterns over API reference
    • Include runnable examples
    • For complex packages, move advanced topics to references/
  7. Create the skill directory and files:
    • Use Write tool to create SKILL.md
    • Create any necessary reference files
    • No README.md or auxiliary documentation
  8. Validate structure:
    • Confirm YAML frontmatter is valid
    • Check that description is comprehensive and includes triggers
    • Ensure examples are runnable
    • Verify references are properly linked if used

Reference

See references/skill-template.md for the standard structure and references/analysis-guide.md for determining appropriate detail level.

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.