OpenSmartRoute

write-skill - Skill - OpenSmartRoute

Skillv1.0.0

write-skill

Name: write-skill
Author: rene404

Create a new skill following the project's skill conventions — correct frontmatter, SKILL.md structure, flat directory layout, and the README/CHANGELOG updates a new skill requires. Use when the user

by rene404(0) 0 installs

Free

Free account. Installing gives you the manifest plus copy-paste snippets.

See reviews

About

Imported from rene404/workflow-skills (skills/write-skill/SKILL.md). Install upstream with npx skills add rene404/workflow-skills --skill write-skill. Copyright stays with the author.

When to create a skill

A skill is worth creating when:

The workflow recurs across tasks or projects.
The steps are non-obvious and easy to get wrong.
There is a clear trigger phrase (what the user says to invoke it).
It is general enough to work outside the current task's context.

Do not create a skill for a one-time operation, a project-specific script, or something that is already covered by an existing skill.

Process

1. Define the skill

Answer these before writing a single line:

Name: kebab-case identifier (matches directory name)
Trigger: What does the user say or do that should invoke this skill?
Problem: What failure mode or inefficiency does this skill prevent?
Scope: What is explicitly out of scope for this skill?
Related skills: What skills does this complement or hand off to?

2. Write the description

The description is the only thing the agent reads when deciding whether to load this skill.

Rules:

Max 1,024 characters.
Written in third person.
Must include explicit "Use when..." trigger phrases.
Must include "Do NOT use when..." anti-triggers if ambiguity exists.
Be specific — vague descriptions cause incorrect activation.

Template:

[What the skill does in one sentence]. Use when [explicit triggers]. Do NOT use when [anti-triggers].

3. Write SKILL.md

---
name: [kebab-case]
description: [description from Step 2]
argument-hint: [optional — what argument the user can pass]
---

## [Philosophy or purpose — one line]

[Brief philosophy statement]

## [Main section]

[Numbered steps or phases]

## Rules / Anti-patterns

[What NOT to do — at least 2–3 explicit rules]

## Related

- `/skill-name` — [relationship]

4. Create the directory

skills/[skill-name]/SKILL.md

The layout is flat — one directory per skill, no category folders. Supporting files (formats, templates, references) live beside SKILL.md in the same folder.

No manifest edit is needed. Claude Code discovers skills/ automatically, so .claude-plugin/plugin.json carries no skills key at all. The Codex and Cursor manifests point at the directory once ("skills": "./skills/") — they never list individual skills. Adding a per-skill path to any manifest is a bug, not a step.

What does need updating when a skill is added:

README.md — the skill list under "What's in the box"
CHANGELOG.md — an entry under [Unreleased]
the version in all four manifests, if you are cutting a release (see AGENTS.md)

5. Test the description

Read the description aloud. Ask: "If I were the agent and only saw this text, would I know exactly when to use this skill and when not to?" If no, rewrite.

Checklist

/plan — if the skill requires companion scripts or supporting files
/review — review the skill file before committing

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot
curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'

Manifest

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

rene404-workflow-skills-write-skill.ocm.jsonjson

{
  "ocm": "1",
  "id": "rene404-workflow-skills-write-skill",
  "kind": "skill",
  "name": "write-skill",
  "description": "Create a new skill following the project's skill conventions — correct frontmatter, SKILL.md structure, flat directory layout, and the README/CHANGELOG updates a new skill requires. Use when the user wants to add a new skill, says \"write a skill for X\", or needs to capture a repeatable workflow as a reusable skill. Do NOT use for one-time operations, project-specific scripts, or workflows already covered by an existing skill.",
  "publisher": "rene404",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "general"
    ],
    "tags": [
      "skill-md",
      "github"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "Create a new skill following the project's skill conventions — correct frontmatter, SKILL.md structure, flat directory layout, and the README/CHANGELOG updates a new skill requires. Use when the user wants to add a new skill, says \"write a skill for X\", or needs to capture a repeatable workflow as a reusable skill. Do NOT use for one-time operations, project-specific scripts, or workflows already covered by an existing skill."
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "github",
      "repository": "https://github.com/rene404/workflow-skills",
      "path": "skills/write-skill/SKILL.md",
      "ref": "5616bcc2c1dfc56e06deb5425e213f08278a13e8",
      "url": "https://github.com/rene404/workflow-skills/blob/5616bcc2c1dfc56e06deb5425e213f08278a13e8/skills/write-skill/SKILL.md",
      "key": "rene404/workflow-skills/skills/write-skill/SKILL.md"
    }
  },
  "instructions": "## When to create a skill\n\nA skill is worth creating when:\n- The workflow recurs across tasks or projects.\n- The steps are non-obvious and easy to get wrong.\n- There is a clear trigger phrase (what the user says to invoke it).\n- It is general enough to work outside the current task's context.\n\nDo not create a skill for a one-time operation, a project-specific script, or\nsomething that is already covered by an existing skill.\n\n## Process\n\n### 1. Define the skill\n\nAnswer these before writing a single line:\n- **Name:** kebab-case identifier (matches directory name)\n- **Trigger:** What does the us",
  "cost": {
    "context_tokens": 848
  }
}

Fetch it by URL: GET /api/v1/registry/rene404-workflow-skills-write-skill/manifest?version=1.0.0