skill-seekers — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited skill-seekers (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Convert any documentation source into a Claude skill.
Before writing anything, understand what the source contains:
Choose the right skill structure based on the source:
| Source Type | Best Skill Structure |
|---|---|
| API Reference | Cheat sheet + common patterns |
| Framework docs | Workflow guide + gotchas |
| GitHub README | Quickstart + architecture notes |
| Tutorial | Distilled steps + adaptation notes |
| Design system | Component usage + constraints |
Prioritize:
Do NOT include:
Template:
---
name: [kebab-case-name]
description: [Third-person trigger description. When to use this skill.
Include key action verbs: "Use when building X", "Use when the user
asks about Y", "Activate when working with Z". Be specific about triggers.]
---
# [Tool/Framework Name] Reference
## Quick Patterns
### [Most common task 1]
[Code example or steps]
### [Most common task 2]
[Code example or steps]
### [Most common task 3]
[Code example or steps]
## Key Concepts
[The 3-5 concepts that unlock everything else. Not a glossary — only what changes behavior.]
## Gotchas & Non-Obvious Behavior
- [Gotcha 1]: [What it is, why it matters, how to handle it]
- [Gotcha 2]: ...
- [Gotcha 3]: ...
## Configuration Reference
[Only the options that actually matter for real usage]
## Common Patterns
[2-3 complete, copy-pasteable examples for typical use cases]
Source: [URL of original documentation]The description field is the most important part. It determines when Claude loads the skill.
Good description: "Use when building FastAPI applications, defining routes, handling authentication, writing Pydantic models, or when the user asks how to do anything with FastAPI."
Bad description: "A reference skill for FastAPI that contains patterns and examples."
Rules for the description:
When the user provides a URL or names a documentation source:
Source: adapted from yusufkaraaslan/Skill_Seekers concept
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.