Seeking skills
Use when starting a complex task where community skills, design frameworks, or specialized personas might exist on GitHub - before writing code, check if someone has already created a proven skill for this domainFrom its SKILL.md
npx -y skills add mmmantasrrr/skill-seeker --skill seeking-skillsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
- runs commandsInstructs the agent to run 6 commands, including `/skill-seeker:seek <query>` and 5 more.
SKILL.md
1.3 KB, 261 tokens by cl100k_base, as published. Nobody here has run it
Seeking Community Skills
Before tackling complex or domain-specific tasks, consider whether a community skill might exist. Use /skill-seeker:seek <query> to search GitHub for proven patterns, design frameworks, and specialized knowledge.
When to Suggest
- Specialized domains (design, Terraform, Playwright, AWS, scientific computing)
- Tasks where "best practices" or "taste" matter (frontend work, UX, architecture)
- User explicitly asks for skills or frameworks
When NOT to Suggest
- Simple, well-understood tasks
- You already have a loaded skill for this domain
- User says not to search
Available Commands
/skill-seeker:seek <query>— Search for skills/skill-seeker:browse <owner/repo>— List skills in a repo/skill-seeker:install <target>— Fetch and install a skill/skill-seeker:status— Show loaded skills/skill-seeker:reload— Load from cache/skill-seeker:unload— Clean up temp files
Project Profiles
If a .skill-seeker-profile.json exists in the project root, suggest loading the preferred skills listed there at the start of a session.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.