Install
$ agentstack add skill-jajupmochi-agent-harness-new-skill ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
/new-skill
Scaffold a new skill following the Claude Code SKILL.md spec.
Usage
/new-skill /
E.g.: /new-skill general/find-duplicates or /new-skill research-pkg/new-experiment
Pre-flight
- Verify
skills///does not already exist - Verify `
is one of:general/,research-pkg/,static-site/,productivity/,personal/` — or ask the user to add a new bucket if needed
> ⚠️ Claude Code plugin discovery is TOP-LEVEL only. CC auto-discovers skills//SKILL.md one level > deep — it does NOT scan skills///. So a skill you want Claude to auto-discover MUST live at > the top level skills// (like memory-flywheel, tui-installer, figma-design-fetch). The > skills/general/* copies are reached by Codex (skills/ glob) and opencode (deploy-skills), NOT by the CC > plugin. If the skill should be Claude-discoverable, create it at skills// (bucket is then just > an organizational tag in INVENTORY, not a path level).
Steps
- Create directory:
``bash mkdir -p skills// ``
- Ask the user for:
- One-line description (becomes
description:frontmatter — this is what Claude reads to decide auto-invocation) - Trigger:
auto(Claude invokes when matched) / slash-only (user must type/) / both - Skill body content — what does the skill do?
- Write
skills///SKILL.md:
```markdown --- name: description: disable-model-invocation: true ---
# /
## Master TOC
- [Pre-flight](#pre-flight)
- [Steps](#steps)
- [Notes for the agent](#notes-for-the-agent)
- [Companion](#companion)
## Pre-flight
## Steps
...
## Notes for the agent
## Companion
```
- Update
skills/README.md— add a row to the skill index table.
- Update
INVENTORY.mdANDINVENTORY.zh.md— add a row to the Skills section.
- Show the user the diff and ask for confirmation before committing.
Frontmatter conventions
name— kebab-case, matches the directory namedescription— be specific about WHEN the skill fires. Claude uses this to decide auto-invocation. Vague descriptions cause both false positives and false negatives.disable-model-invocation: true— set for skills with side effects (deploy, force-push, etc.) that should only fire on explicit user request
Companion
docs/CONTRIBUTING.md§"Adding a skill" — formal specskills/README.md— index of all skills + bucket conventions- Anthropic's
skill-creatorplugin — for more sophisticated skill authoring with evals
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: jajupmochi
- Source: jajupmochi/agent-harness
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.