Skip to content
Agentmart
Submit a tool

skill-authoring

When you notice a reusable multi-step task worth saving, or the user asks you to save, change, or delete a skill.

Skill by mitch-zink

IndexedApache-2.0
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/mitch-zink-skill-authoring

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

When you notice a reusable multi-step task worth saving, or the user asks you to save, change, or delete a skill.

Use cases: productivity

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/skill-authoring

What's inside

Skill name
skill-authoring
Description
When you notice a reusable multi-step task worth saving, or the user asks you to save, change, or delete a skill.
License
Apache-2.0
Instructions
24 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Skill authoring

A skill is `skills/<slug>/SKILL.md`: YAML frontmatter, then a markdown recipe. Same format as Claude Code skills.

```
---
name: daily-standup
description: One line on WHEN to use this skill (required)
---
# Steps
1. ...
```

- **Save without asking** when a multi-step task is clearly reusable and unambiguous, then mention it. Ask first only when it is unclear the task will recur.
- **The description is the trigger.** It is the only thing read when deciding to run the skill, so say when it applies, not what it is.
- **Keep it generic.** Which channel, which table, which team belong in the routine that runs the skill, not the skill. A skill should survive being shared as a template.
- **Leave unknown frontmatter keys alone** (`globs`, `alwaysApply`, `metadata`). Other runtimes use them.
- **Deleting is global.** Confirm with the user first.
- Helper files (scripts, references) go next to `SKILL.md` and are referenced by relative path.
- Skills installed from a plugin or marketplace are read-only. Manage them by installing or uninstalling, never by editing.

## Keep skills honest
During skill review (see `self_improvement/README.md`), audit each skill against how recent runs actually went. Fix what drifted. Retire a skill that measurably doesn't help.

From mitch-zink/agent-template, Apache-2.0.

More from mitch-zink/agent-template

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Oct 6, 2026 (22 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License
Apache-2.0
Repository
github.com/mitch-zink/agent-template
First seen
Oct 24, 2026
Last checked
Oct 24, 2026
Source
GitHubgithub-graphql

More from mitch-zink

Cite this page

skill-authoring. Agent Mart. https://agentmart.dev/skills/mitch-zink-skill-authoring (last updated 2026-10-24)