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.
In this repository5 other files it gives its agents.
- biome-lint-formatSkill
- cut-releaseSkill
- go-service-scaffolderSkill
- react-spa-viteSkill
- writing-qualitySkill
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
- Distinctive: line 20
If the package has multiple subpackages, fetch the most relevant ones
- Very specific: line 28
Name: Use go- and the last segment of import path (e.g., jwx from github.com/lestrrat-go/jwx/v3)
- Very specific: line 29
If name is too generic (like http or json), prepend with package scope (e.g., go-fasthttp)
- Distinctive: line 33
When to trigger: "Use when working with [domain], [specific task], or when the user mentions [package name]"
- Distinctive: line 44
Keep under 500 lines if possible
- Very specific: line 50
Use Write tool to create SKILL.md
- Distinctive: line 51
Create any necessary reference files
- Distinctive: line 52
No README.md or auxiliary documentation
- Distinctive: line 56
Check that description is comprehensive and includes triggers
- Distinctive: line 57
Ensure examples are runnable
- Distinctive: line 58
Verify references are properly linked if used
≈ “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.
Files
Go Package Skill Creator
Generate skills that teach how to use specific Go packages.
Workflow
- 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)
- Package import path (e.g.,
- 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
- Get package documentation from
- 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
- Derive skill identity:
- Name: Use
go-and the last segment of import path (e.g.,jwxfromgithub.com/lestrrat-go/jwx/v3)- If name is too generic (like
httporjson), prepend with package scope (e.g.,go-fasthttp)
- If name is too generic (like
- 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]"
- Name: Use
- Create skill structure:
<package-name>/ ├── SKILL.md └── references/ (optional, only if complex) └── advanced.md - 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/
- Create the skill directory and files:
- Use Write tool to create SKILL.md
- Create any necessary reference files
- No README.md or auxiliary documentation
- 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.
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.

