メニュー
Use when the user asks to author, draft, scaffold, or create a new Agent Skill or SKILL.md file. Produces a spec-compliant skill folder ready to submit or use locally with Claude.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/nimaaksoy/nimaaksoy.com --skill create-a-new-skillコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
Use when drafting a cold B2B outreach email. Produces a short message with one specific hook, one line of relevance, and a soft, low-commitment call to action.
Use when the user gives a subject, story, or text and asks for a Persian / Farsi poem. Produces a poem in a chosen classical style (Saadi, Hafez, Rumi, Ferdowsi, Khayyam, modern) with meter and rhyme.
Use when generating prompts for AI video tools (Sora, Runway, Veo, Kling, Pika) to create hypnotic 3–5 second loop videos for music. Produces atmospheric, loop-friendly visual briefs.
| name | Create a New Skill |
| description | Use when the user asks to author, draft, scaffold, or create a new Agent Skill or SKILL.md file. Produces a spec-compliant skill folder ready to submit or use locally with Claude. |
| dependencies | [] |
| category | meta |
| subcategory | skill-authoring |
| tags | ["skill-authoring","meta","agent-skills","template","scaffolding"] |
| author | {"name":"Nima Aksoy","url":"https://nimaaksoy.com","github":"nimaaksoy"} |
| license | CC-BY-4.0 |
| version | 0.1.0 |
| created | 2026-05-14T00:00:00.000Z |
| updated | 2026-05-14T00:00:00.000Z |
A skill that helps you write a new skill. Given a topic, behaviour, or workflow the user wants to encode, produce a complete SKILL.md plus folder structure that follows Anthropic's Agent Skills spec exactly — and, when the target is skills.nimaaksoy.com, also satisfies that directory's extra metadata and validation rules.
The output is a working folder a contributor can drop into skills/<category>/<subcategory>/<slug>/, run npm run validate against, and submit as a PR.
skills.nimaaksoy.com and wants help authoring a submission.Do not use this skill when:
Work in this order. Don't skip steps — they're sequenced so the description (the part that controls whether the skill ever loads) gets written before anything else is committed.
Before writing anything, get clear on the single condition that should make a model load this skill. Ask the user, in plain language:
"When should this skill activate? Describe the user's request or the situation that signals it's needed — not what the skill does, but what the user is asking for when it should fire."
If the user can't articulate a trigger in one sentence, the skill is probably too broad or not actually skill-shaped. Push back and offer to narrow it.
descriptionThis is the single most important field. The model uses it to decide whether to load the skill at all.
Rules:
See resources/description-examples.md for good and bad examples.
cold-email-outreach.)For submissions to skills.nimaaksoy.com, the category and subcategory must match categories.yml exactly. See resources/categories.md for the current tree.
A skill belongs to exactly one category + subcategory. If two feel equally right, pick the one closer to where a user would look for it, and add the other angle as a tag.
Start from resources/template.md. Fill in:
---
name: <Skill Name>
description: <single-line trigger description, ≤ 200 chars>
dependencies: [] # only if real (e.g. ["python>=3.10"])
# Directory-only fields — ignored by Claude, used by the site
category: <category-id> # must exist in categories.yml
subcategory: <subcategory-id> # must exist under that category
tags: [<1-8 kebab-case>]
author:
name: <Author Name>
url: <optional>
github: <optional>
license: CC-BY-4.0 # default; only change if needed
version: 0.1.0
created: <YYYY-MM-DD>
updated: <YYYY-MM-DD>
---
If you don't know the author, ask. Don't guess — the field is required.
Use these headings, in this order. The validator requires at least one ## heading; convention requires the full set:
## Overview — one paragraph: what this skill does and the situation it's built for. Written so a contributor browsing the directory understands the point in under 10 seconds.## When to use this skill — a bullet list of trigger conditions, and (recommended) a "Do not use" sub-list.## Instructions — step-by-step guidance for the model. Be concrete. Reference any files under resources/ by relative path.## Examples — at least one worked example, ideally two. Use the ### Example 1 — label pattern. For each: an Input block (what the user says) and an Expected behaviour block (what the model should do).## Resources — describe each file under resources/.## Notes & limitations — what the skill can't do, common pitfalls, things to push back on.## Changelog — append-only version log.Don't pad the folder. A resource file is worth keeping only if:
Instructions would crowd the body.If a "resource" is just a paragraph of text, fold it into Instructions.
Before declaring the skill done, walk the checklist in resources/checklist.md. The site validator enforces these on every PR:
name ≤ 64 chars; description ≤ 200 chars.category and subcategory exist in categories.yml.tags is 1–8 kebab-case strings.author.name present.skills/<category>/<subcategory>/<slug>/, slug kebab-case.## heading.SKILL.md.The deliverable is a folder, not just a SKILL.md. Produce:
<slug>/
SKILL.md
README.md # optional but recommended for non-trivial skills
resources/ # only if step 7 said yes
<file>
LICENSE.txt # only if not CC-BY-4.0
Then tell the user how to ship it:
# from the repo root
npm run validate # confirms it passes the same checks CI will run
git add skills/<cat>/<sub>/<slug>
git commit -m "Add <name> skill"
# open a PR
Input:
"I keep writing the same kind of bug report — title, repro steps, expected, actual, environment. Can you turn that into a skill?"
Expected behaviour:
The model should:
category: software, subcategory: qa-testing (or code-review if more fitting — confirm with user).Instructions that walk through the five-field structure, with a one-line rule for each.resources/template.md with the empty bug-report skeleton, since it's verbatim content the model copies.Examples: one minimal bug, one complex bug with multiple repro steps.Input:
"Make me a skill that's good at everything coding."
Expected behaviour:
The model should not scaffold a skill. Instead it should respond:
"Skills work best when they trigger on a specific situation. 'Everything coding' is too broad — the model wouldn't know when to load it, and once loaded it would compete with general coding behaviour Claude already does well. What's the narrowest version of this? E.g. 'review a Python diff for type-safety issues', 'turn a stack trace into a 3-line root-cause hypothesis', 'write a SQL migration with rollback'. Pick one and we'll author that."
Only proceed once the user has scoped the skill to a real trigger.
Input:
"Help me submit a skill to skills.nimaaksoy.com for writing investor update emails."
Expected behaviour:
The model should:
business / sales? business / finance? Likely business / finance since investor updates are a finance-team workflow; ask the user if unsure.skills/business/finance/investor-update-email/.npm run validate, then open a PR using the template in .github/PULL_REQUEST_TEMPLATE.md.resources/template.md — the canonical empty SKILL.md template. Copy verbatim, then fill in.resources/description-examples.md — good vs bad description field examples, with reasons.resources/checklist.md — the validator's full rule list as a checkbox list. Walk it before declaring done.resources/categories.md — flat reference of all category + subcategory ids from categories.yml.description alone. If the skill never triggers in practice, the description is the first thing to revise — body changes won't help.Instructions. resources/ is for templates, examples, and reference data the model loads on demand.skills.nimaaksoy.com. If you're authoring for a different directory or for personal use, ignore the directory-only frontmatter fields — Claude does.0.1.0 — initial version.