Hermes Agent Skill Authoring
NousResearch/hermes-agent
Author in-repo SKILL.md files: frontmatter and structure. An agent skill from NousResearch/hermes-agent.
A skill your agent uses when a description frontmatter field must become an accurate activation trigger, especially because its skill stays dormant or is confused with a sibling—encode recognizable…
MITAuto-check passed
Install Skill Description Trigger Authoring
$ npx skills add mtarcure/claude-vibe-squad --skill skill-description-trigger-authoring -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mtarcure/claude-vibe-squad skill-description-trigger-authoring --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mtarcure/claude-vibe-squad.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/skill-description-trigger-authoring .claude/skills/skill-description-trigger-authoring && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "skill-description-trigger-authoring" agent skill from https://github.com/mtarcure/claude-vibe-squad/tree/main/.agents/skills/skill-description-trigger-authoring into .claude/skills/skill-description-trigger-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-description-trigger-authoring", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mtarcure/claude-vibe-squad/tree/main/.agents/skills/skill-description-trigger-authoringType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mtarcure/claude-vibe-squad --skill skill-description-trigger-authoring -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mtarcure/claude-vibe-squad skill-description-trigger-authoring --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mtarcure/claude-vibe-squad.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/skill-description-trigger-authoring .agents/skills/skill-description-trigger-authoring && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "skill-description-trigger-authoring" agent skill from https://github.com/mtarcure/claude-vibe-squad/tree/main/.agents/skills/skill-description-trigger-authoring into .agents/skills/skill-description-trigger-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-description-trigger-authoring", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mtarcure/claude-vibe-squad --skill skill-description-trigger-authoring -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mtarcure/claude-vibe-squad skill-description-trigger-authoring --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mtarcure/claude-vibe-squad.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/skill-description-trigger-authoring .cursor/skills/skill-description-trigger-authoring && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "skill-description-trigger-authoring" agent skill from https://github.com/mtarcure/claude-vibe-squad/tree/main/.agents/skills/skill-description-trigger-authoring into .cursor/skills/skill-description-trigger-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-description-trigger-authoring", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mtarcure/claude-vibe-squad.git --path .agents/skills/skill-description-trigger-authoring--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mtarcure/claude-vibe-squad --skill skill-description-trigger-authoring -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mtarcure/claude-vibe-squad skill-description-trigger-authoring --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mtarcure/claude-vibe-squad.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/skill-description-trigger-authoring .gemini/skills/skill-description-trigger-authoring && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "skill-description-trigger-authoring" agent skill from https://github.com/mtarcure/claude-vibe-squad/tree/main/.agents/skills/skill-description-trigger-authoring into .gemini/skills/skill-description-trigger-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-description-trigger-authoring", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mtarcure/claude-vibe-squad skill-description-trigger-authoringInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mtarcure/claude-vibe-squad --skill skill-description-trigger-authoring -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mtarcure/claude-vibe-squad.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/skill-description-trigger-authoring .github/skills/skill-description-trigger-authoring && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "skill-description-trigger-authoring" agent skill from https://github.com/mtarcure/claude-vibe-squad/tree/main/.agents/skills/skill-description-trigger-authoring into .github/skills/skill-description-trigger-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-description-trigger-authoring", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mtarcure/claude-vibe-squad --skill skill-description-trigger-authoring -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mtarcure/claude-vibe-squad skill-description-trigger-authoring --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mtarcure/claude-vibe-squad.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/skill-description-trigger-authoring .opencode/skills/skill-description-trigger-authoring && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "skill-description-trigger-authoring" agent skill from https://github.com/mtarcure/claude-vibe-squad/tree/main/.agents/skills/skill-description-trigger-authoring into .opencode/skills/skill-description-trigger-authoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-description-trigger-authoring", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
skill-description-trigger-authoring- GitHub stars
- 162
- Token cost
- ~1.1k tokens
- SKILL.md length
- 607 words
- Files
- 1
- Skills in repo
- 17
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when a description frontmatter field must become an accurate activation trigger, especially because its skill stays dormant or is confused with a sibling—encode recognizable…
- Works in 7 steps: Enumerate the firing situations: what is… → Write from the reader's pre-skill state.… → Front-load the trigger. Descriptions are… → …
- A description frontmatter field must become an accurate activation trigger
- SKILL.md covers When to use, Inputs, Steps and Outputs, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Skill Description Trigger Authoring is an agent skill from mtarcure/claude-vibe-squad. Use when a description frontmatter field must become an accurate activation trigger, especially because its skill stays dormant or is confused with a sibling—encode recognizable workflow cues and replay-test positive and negative tasks. Scope is trigger metadata, not instruction-body or resource design.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Multi-model AI orchestration where behaviour is Markdown, not code. One coordinator routes scoped task packets to 71 role-based specialists across 5 model families (Codex /… The licence is MIT.
When your agent uses it
- A description frontmatter field must become an accurate activation trigger
- Especially because its skill stays dormant
- Is confused with a sibling—encode recognizable workflow cues and replay-test positive and negative tasks
- Not instruction-body
Example prompts
- “/skill-description-trigger-authoring”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Enumerate the firing situations: what is the practitioner doing or about to do when this skill must load? Situations, not topics — "about…
- Write from the reader's pre-skill state. They can recognize their situation; they cannot recognize the method's vocabulary. "Use when…
- Front-load the trigger. Descriptions are scanned under time pressure; the first clause decides whether the rest is read.
- Include the concrete cue words and symptoms as they appear in real tasks — the phrases in packets, the moment in the workflow, the…
- Add anti-triggers where siblings overlap: when NOT to use this skill, and which sibling handles that case. Disambiguation in the…
- Keep it to one or two sentences. A trigger buried in a paragraph fires never; completeness belongs in the body's When-to-use, not the…
- Replay-test: take three real past tasks where the skill should have fired and two adjacent ones where it shouldn't. Reading the…
What it can do on your machine
Read from SKILL.md and the folder at commit 7bd69f8. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Skill Description Trigger Authoring loads about 1.1k tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 607 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mtarcure/claude-vibe-squad at commit 7bd69f8, republished under its MIT licence (© mtarcure). 607 words, ~1,129 tokens.
Download SKILL.mdSave it as
.claude/skills/skill-description-trigger-authoring/SKILL.md (or your agent's skills folder).- name
- skill-description-trigger-authoring
- description
- Use when a description frontmatter field must become an accurate activation trigger, especially because its skill stays dormant or is confused with a sibling—encode recognizable workflow cues and replay-test positive and negative tasks. Scope is trigger metadata, not instruction-body or resource design.
- audience
- specialist
Skill Description Trigger Authoring
A skill's description is its activation surface: it is matched against the task at hand by a reader who does not yet know the method. A description that summarizes content instead of naming the firing situation produces a skill that is technically available and practically never loaded.
When to use
- Authoring or revising the
description:frontmatter of any skill. - A postmortem shows a task where an existing skill should have fired and didn't.
- Two adjacent skills keep being confused for each other.
Inputs
- The moments in real workflows when the skill must load ("about to emit
complete", "about to implement against a foreign schema"). - Real past tasks: several where the skill should have fired, several adjacent ones where it should not.
Steps
- Enumerate the firing situations: what is the practitioner doing or about to do when this skill must load? Situations, not topics — "about to claim done", not "quality assurance".
- Write from the reader's pre-skill state. They can recognize their situation; they cannot recognize the method's vocabulary. "Use when about to X" beats "a methodology for X-ing".
- Front-load the trigger. Descriptions are scanned under time pressure; the first clause decides whether the rest is read.
- Include the concrete cue words and symptoms as they appear in real tasks — the phrases in packets, the moment in the workflow, the observable temptation ("it should work"). Matching happens against the task's own language.
- Add anti-triggers where siblings overlap: when NOT to use this skill, and which sibling handles that case. Disambiguation in the description is cheaper than a wrong load.
- Keep it to one or two sentences. A trigger buried in a paragraph fires never; completeness belongs in the body's When-to-use, not the description.
- Replay-test: take three real past tasks where the skill should have fired and two adjacent ones where it shouldn't. Reading the description alone — no body — check it routes all five correctly. A miss is a description bug; fix the description, not the tasks.
Outputs
- A one-to-two-sentence description whose first clause names the firing situation, containing real cue language, and disambiguated from siblings.
- A recorded replay-test result.
Show full SKILL.md (249 more words)Show less
Failure modes
- Summary-not-trigger — "Guidance on verification best practices": describes the content, names no moment, never fires.
- Method leakage — the description teaches steps instead of naming situations, wasting its only job on content the body already carries.
- Over-broad trigger — fires on everything, reader learns to ignore it; a trigger that always matches carries no information.
- Post-skill vocabulary — jargon the method itself introduces; the pre-skill reader can't match terms they haven't learned yet.
- Missing anti-trigger — two siblings with overlapping triggers, so the wrong one loads and both lose trust.
Worked example
Bad: description: Describes the verification methodology for completed work. — a summary; no practitioner mid-task self-identifies as "needing verification methodology". Good: description: Use when about to claim work is complete, fixed, or passing — run the check that would falsify each claim and read its output before emitting the claim. The first clause names the exact workflow moment (emitting a completion claim); "complete, fixed, or passing" are the literal words that appear in the task's own language; the em-dash clause states the obligation compactly without teaching the method. Replay-test: fires on "flip the registry rows and confirm validators green" (should), fires on "report the fix upstream" (should), stays silent on "estimate the refactor scope" (correctly — that's scope-decomposition's trigger).
Acceptance
- The replay test routes all sampled tasks correctly from the description alone.
- The first clause states a situation the pre-skill reader can recognize.
- Length is at most two sentences; cue phrases are real task language, not method jargon.
- Overlapping siblings are explicitly disambiguated.
© mtarcure, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/skill-description-trigger-authoring of mtarcure/claude-vibe-squad.
Open the folder on GitHubat commit 7bd69f8
Compare with similar skills
Skill Description Trigger Authoring next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Skill Description Trigger Authoring this skillmtarcure/claude-vibe-squad | 162 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Hermes Agent Skill AuthoringNousResearch/hermes-agent | 252k | — | ~3.6k | Automated safety check: Pass | MIT | |
| Configuring Oauth2 Authorization Flowmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Containing Active Breachmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~2.7k | Automated safety check: Pass | Apache-2.0 | |
| Duplicate Descriptionthedaviddias/Front-End-Checklist | 74k | — | ~695 | Automated safety check: Pass | MIT | |
| Implementing GCP Binary Authorizationmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~2k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Configuring Oauth2 Authorization Flow
mukul975/Anthropic-Cybersecurity-Skills
Configures secure OAuth 2.0 authorization flows, including Authorization Code with PKCE, Client Credentials, and Device Authorization Grant, covering flow selection, PKCE implementation, token…
Containing Active Breach
mukul975/Anthropic-Cybersecurity-Skills
Executes containment strategies to stop active adversary operations and prevent lateral movement during a confirmed security breach.
Duplicate Description
thedaviddias/Front-End-Checklist
A skill your agent uses when auditing a site's meta tag uniqueness, generating page-specific meta descriptions, or reviewing CMS templates that inject the same description globally.
Implementing GCP Binary Authorization
mukul975/Anthropic-Cybersecurity-Skills
Implements GCP Binary Authorization end to end, including creating KMS-backed attestors, Container Analysis notes, deploy-time policies, and signing image attestations, so that only trusted…
Collectors Authoring
netdata/netdata
Author, modify, or review Netdata collectors across Go, IBM, C, Rust and external plugins.
More from mtarcure/claude-vibe-squad
All 17 skills in this repoSystematic Attacking
mtarcure/claude-vibe-squad
A skill your agent uses for ALL authorized offensive-security / bug-bounty work — the single method to find, chain, prove, dedup, and package the highest-value (High/Critical) findings across every…
Blind Rediscovery
mtarcure/claude-vibe-squad
Operational checklist + helper for blind-rediscovery fan-out work.
Chain Construct Smart Contract
mtarcure/claude-vibe-squad
A skill your agent uses when you have a confirmed on-chain vulnerability hypothesis and must demonstrate it with a passing proof-of-concept — author an attacker contract or crafted instruction…
Compact Now
mtarcure/claude-vibe-squad
Operator-triggered proactive compaction — Chrono externalizes load-bearing state (active decisions, open tasks, next action) to a snapshot + a durable Vault learning note before invoking Claude…
Agent Prompt Engineering
mtarcure/claude-vibe-squad
A skill your agent uses when building or revising the system prompt for a product agent and you need an eval-backed boundary, tool-use, grounding, and output contract.
Defi Invariant Check
mtarcure/claude-vibe-squad
A skill your agent uses when the audit target is a DeFi protocol — AMM, lending market, yield vault, stablecoin, or perps — and you must author the economic properties generic campaigns miss, such…
Questions about Skill Description Trigger Authoring
What does Skill Description Trigger Authoring do?
A skill your agent uses when a description frontmatter field must become an accurate activation trigger, especially because its skill stays dormant or is confused with a sibling—encode recognizable…. Skill Description Trigger Authoring is an agent skill from mtarcure/claude-vibe-squad. Use when a description frontmatter field must become an accurate activation trigger, especially because its skill stays dormant or is confused with a sibling—encode recognizable workflow cues and replay-test positive and negative tasks.
When should I use Skill Description Trigger Authoring?
Skill Description Trigger Authoring fits situations like: A description frontmatter field must become an accurate activation trigger; especially because its skill stays dormant; is confused with a sibling—encode recognizable workflow cues and replay-test positive and negative tasks; not instruction-body.
How do I install Skill Description Trigger Authoring in Claude Code?
Run `npx skills add mtarcure/claude-vibe-squad --skill skill-description-trigger-authoring -a claude-code`. Or copy the skill folder (.agents/skills/skill-description-trigger-authoring in mtarcure/claude-vibe-squad) into .claude/skills/skill-description-trigger-authoring in your project. Claude Code loads it when a task matches its description.
How do I install Skill Description Trigger Authoring in Codex?
Run `npx skills add mtarcure/claude-vibe-squad --skill skill-description-trigger-authoring -a codex`. Or copy the skill folder (.agents/skills/skill-description-trigger-authoring in mtarcure/claude-vibe-squad) into .agents/skills/skill-description-trigger-authoring in your project. Codex loads it when a task matches its description.
Can I use Skill Description Trigger Authoring in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mtarcure/claude-vibe-squad --skill skill-description-trigger-authoring -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/skill-description-trigger-authoring, .gemini/skills/skill-description-trigger-authoring, .github/skills/skill-description-trigger-authoring and .opencode/skills/skill-description-trigger-authoring in your project.
What does Skill Description Trigger Authoring need to run?
SKILL.md names no scripts, command-line tools or credentials: Skill Description Trigger Authoring is instructions for the agent only.
Does Skill Description Trigger Authoring access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Skill Description Trigger Authoring safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Skill Description Trigger Authoring use?
Skill Description Trigger Authoring is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Skill Description Trigger Authoring use?
About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Skill Description Trigger Authoring?
Skills that share tags, products or a category with Skill Description Trigger Authoring: Hermes Agent Skill Authoring (NousResearch/hermes-agent, 252k stars), Configuring Oauth2 Authorization Flow (mukul975/Anthropic-Cybersecurity-Skills, 34k stars), Containing Active Breach (mukul975/Anthropic-Cybersecurity-Skills, 34k stars) and Duplicate Description (thedaviddias/Front-End-Checklist, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Skill Description Trigger Authoring?
mtarcure (a GitHub user) maintains it in mtarcure/claude-vibe-squad, which has 162 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on September 21, 2026.
Source: mtarcure/claude-vibe-squad on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.