agentsclimarketplace
Sign in

Write a skill

Skill RubenGlez/harness/skills/write-a-skill

Create new harness skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.From its SKILL.md

Install
npx -y skills add RubenGlez/harness --skill write-a-skill

Assembled 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 2 commands, including `/reload-skills` and 1 more.

SKILL.md

4.6 KB, ~1.0k tokens by cl100k_base, as published. Nobody here has run it

Writing Skills

Skills live in skills/<name>/ within this repo and are available as harness:<name> once installed. In Claude Code, run /reload-skills to pick up a new one mid-session; for Codex, run bash update.sh to symlink it into ~/.codex/skills/.

Process

  1. Gather requirements - ask user about:

    • What task/domain does the skill cover?
    • What specific use cases should it handle?
    • Does it need executable scripts or just instructions?
    • Any reference materials to include?

  2. Draft the skill - create:

    • skills/<name>/SKILL.md with concise instructions
    • Additional reference files if content exceeds 500 lines
    • Utility scripts if deterministic operations needed

  3. Review with user - present draft and ask:

    • Does this cover your use cases?
    • Anything missing or unclear?
    • Should any section be more/less detailed?

Skill Structure

skills/skill-name/
├── SKILL.md           # Main instructions (required)
├── REFERENCE.md       # Detailed docs (if needed)
├── EXAMPLES.md        # Usage examples (if needed)
└── scripts/           # Utility scripts (if needed)
    └── helper.js

SKILL.md Template

---
name: skill-name
description: Brief description of capability. Use when [specific triggers].
---

# Skill Name

## Quick start

[Minimal working example]

## Workflows

[Step-by-step processes with checklists for complex tasks]

## Advanced features

[Link to separate files: See [REFERENCE.md](REFERENCE.md)]

Description Requirements

The description is the only thing your agent sees when deciding which skill to load. It's surfaced in the system prompt alongside all other installed skills. Your agent reads these descriptions and picks the relevant skill based on the user's request.

Goal: Give your agent just enough info to know:

  1. What capability this skill provides
  2. When/why to trigger it (specific keywords, contexts, file types)

Format:

  • Max 1024 chars
  • Write in third person
  • First sentence: what it does
  • Second sentence: "Use when [specific triggers]"

Good example:

Extract text and tables from PDF files, fill forms, merge documents. Use when working with PDF files or when user mentions PDFs, forms, or document extraction.

Bad example:

Helps with documents.

When to Add Scripts

Add utility scripts when:

  • Operation is deterministic (validation, formatting)
  • Same code would be generated repeatedly
  • Errors need explicit handling

Scripts save tokens and improve reliability vs generated code.

When to Split Files

Split into separate files when:

  • SKILL.md outgrows the core workflow (~120 lines) — move templates, long examples, and reference detail to REFERENCE.md
  • Content has distinct domains
  • Advanced features are rarely needed

Harness Conventions

Workflow vs. standalone — decide before drafting:

  • Workflow skill: fits in the ideate → ship chain. End with a recommended next step (e.g. "Run /qa to verify."). The user invokes it at a specific phase.
  • Standalone skill: callable at any time, independent of phase (e.g. /improve-codebase-architecture, /task). Don't recommend a "next step" — just report what was done.

Harness doc paths — if the skill reads or writes project state, use these standard locations:

  • .harness/product/CONTEXT.md — domain vocabulary; use exact terms in all output and generated code
  • .harness/product/ — product.md, roadmap.md, ux.md, competitors.md
  • .harness/engineering/ — architecture.md, implementation-plan.md, features/
  • .harness/adr/ — architectural decision records
  • .harness/qa/report.md — QA output

Subagents — when spawning subagents, pass file paths, not file contents. Subagents have full repo access. Only pass content directly for small, critical excerpts (e.g. the full text of a feature spec the agent must implement).

Cross-skill references — link to other skills' docs with relative paths (e.g. ../dev-plan/REFERENCE.md).

Review Checklist

After drafting, verify:

  • Description includes triggers ("Use when...")
  • SKILL.md holds the workflow; templates, long examples, and reference detail live in REFERENCE.md
  • Workflow vs. standalone positioning is clear
  • Harness doc paths used where relevant
  • No time-sensitive info
  • Consistent terminology
  • Concrete examples included
  • References one level deep

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 1 of the 12 instructions most docs writing skills give in ~1.0k tokens

Counted across 1,951 of the 3,904 authors here whose files we hold, read 2026-09-06

  • Use third-person for skill descriptionshere, and in 54 of 1951, across 35 files
  • Start descriptions with Use whenin 43 of 1951, across 29 files
  • Run baseline scenarios before writing any skillin 40 of 1951, across 26 files
  • Use active voicein 40 of 1951, across 36 files
  • Map file responsibilities before defining tasksin 36 of 1951, across 29 files
  • Use checkbox syntax for tracking stepsin 35 of 1951, across 27 files
  • Ask one question at a timein 35 of 1951
  • Offer execution options after saving the planin 33 of 1951, across 24 files
  • Include complete code in every stepin 33 of 1951, across 27 files
  • Design units with clear boundaries and interfacesin 31 of 1951, across 23 files
  • Announce the skill usage at the startin 30 of 1951
  • Verify agent compliance after adding the skillin 29 of 1951, across 17 files

Said here and by no other author read

  • use standard harness documentation paths
  • pass file paths to subagents
  • link to other skills using relative paths

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.