skill-authoring
/skill-authoring
Pisze nowy skill jako folder z plikiem SKILL.md i opcjonalnymi skryptami albo poprawia skill, który agent źle wykonuje.
- Autor
- narayana006 ↗
- Repozytorium
- agent-skills-collection ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 10.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 2
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 10.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Pisze nowy skill jako folder z plikiem SKILL.md i opcjonalnymi skryptami albo poprawia skill, który agent źle wykonuje.
Oryginalny opis (EN)
Write a new agent skill or improve an existing one, as a folder with a SKILL.md file and optional scripts. Use when the user asks to create a skill, turn a repeated workflow or set of instructions into a skill, or fix a skill that an agent does not pick up or follows badly.
Jak działa
- Steps
- Common mistakes
Podgląd SKILL.md
---
name: skill-authoring
description: Write a new agent skill or improve an existing one, as a folder with a SKILL.md file and optional scripts. Use when the user asks to create a skill, turn a repeated workflow or set of instructions into a skill, or fix a skill that an agent does not pick up or follows badly.
---
# Writing a skill
A skill is a folder an agent can load when a task matches it. The agent first sees only the
`name` and `description` from the frontmatter; the rest of `SKILL.md` is read once the skill is
chosen, and other files only when the instructions point to them. Write with that in mind.
## Steps
1. **Pin down the job.** Ask for, or write down, two or three concrete requests that should
trigger the skill and what a good result looks like for each. If you cannot, the skill is
too vague to write yet.
2. **Create the folder.** Copy [template.md](template.md) to `<skill-name>/SKILL.md`. The folder
name and the `name` field must be identical: lowercase letters, digits and single hyphens,
at most 64 characters.
3. **Write the description first.** It decides whether the skill is ever used. State what the
skill does, then when to use it, using the words a user would actually type. Plain text, at
most 1024 characters, third person.
- Weak: `Helps with releases.`
- Better: `Write release notes from git history. Use when the user asks for release notes,
a changelog, or what changed since the last release.`
4. **Write the body as instructions to a capable colleague.** Numbered steps for the workflow,
the reasons behind any rule that is not obvious, and the exact output format expected. Leave
out what any competent agent already knows.
5. **Move bulk out of SKILL.md.** Long reference tables, checklists and examples go in their own
files next to it, linked with relative Markdown links. Keep `SKILL.md` under roughly 500 lines.
6. **Script what must be exact.** If a step is mechanical and has to give the same result every
time (parsing, counting, scanning), put it in `scripts/` and tell the agent the exact command.
Scripts should run with a standard interpreter and no installation, read arguments or stdin,
print to stdout and use the exit status to signal failure.
7. **Keep it tool-agnostic.** Do not rely on one agent product's tool names or directory layout.
Refer to bundled files by paths relative to the skill folder, and never link outside it: the
folder gets copied on its own.
8. **Validate.** From the root of this repository:
```bash
skill-lint path/to/skills
```
Fix every error. Read the warnings; they are usually right.
9. **Try it.** Give an agent one of the requests from step 1 with the skill installed. Watch
where it hesitates or goes wrong, and fix the instructions rather than adding more of them.
## Common mistakes
- A description that says what the skill is but not when to use it.
- Instructions written as a wall of rules in capitals instead of steps with reasons.
- Scripts mentioned in the text that were renamed or never added.
- A skill that tries to cover three workflows. Split it.
Pliki w paczce (2)
- SKILL.md 3 KB
- template.md 1 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · narayana006/agent-skills-collection | 100 | MIT |
| TMCP-HUB/project-resolver | 100 | Apache-2.0 |
| contentful/skills | 100 | MIT |
| Esposter/Esposter | 100 | Apache-2.0 |
| komluk/scaffolding | 100 | MIT |
| nyldn/claude-octopus | 100 | MIT |
| redhat-developer/rhdh-skills | 100 | Apache-2.0 |
| tencentcloudbase/cloudbase-ai-toolkit | 100 | MIT |
| ovargas/virtual-team | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 38a74365fd6a (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100create-skill
Tworzy interaktywnie nową umiejętność Grok, czyli plik SKILL.md z opcjonalnymi skryptami i materiałami, po pytaniach do użytkownika. - 100write-project-skill
Tworzy skille agenta, globalne lub lokalne dla projektu, z krótkim SKILL.md i opcjonalnymi skryptami deterministycznymi. - 100agent-skills-authoring
Tworzy lub poprawia przenośny skill agenta dla powtarzalnego procesu: wyzwalacz, instrukcje, materiały referencyjne i plan walidacji. - 100write-a-skill
Tworzy nowy skill agenta z krótkim SKILL.md, opisem wyzwalającym, plikami referencyjnymi i skryptami. - 100skill-creator
Pisze lub przegląda skille: szkicuje nowy SKILL.md ze skryptami, a istniejący audytuje pod kątem słabych wyzwalaczy i przerostu. - 100write-skill
Tworzy nowy skill albo ulepsza istniejący w repozytorium skilli, zgodnie z jego zasadami porządkowania.