Install
$ agentstack add skill-mmusa-second-nature-promote ✓ 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
Promote — the approval gate
Show the user their pending skill proposals and install only the ones they approve. This is the single point where a draft becomes an active skill; it never runs automatically.
Steps
1. List pending proposals
Read ~/.claude/second-nature/proposals/*/. For each, present: proposed name, what it automates (from its SKILL.md description), and the evidence summary (occurrences, sessions, estimated savings from EVIDENCE.md). If there are none, say so and suggest running /harvest.
2. Let the user choose
Ask which to install (all / some / none), and for each approved one whether it should be:
- User-level →
~/.claude/skills//(available in every project) — the default - Project-level →
/.claude/skills//(only makes sense if the pattern is specific to one repo)
The user can also request edits before installing — apply them to the proposal first.
3. Install
For each approved proposal:
- Collision check — if a skill with that name already exists in the target (or an installed plugin exposes one), stop and ask: overwrite, rename, or merge into the existing skill.
- Move the proposal directory's
SKILL.md(and any supporting files, but not EVIDENCE.md) to the target skill directory. - Move the remaining proposal folder to
~/.claude/second-nature/retired/-promoted-/so evidence is preserved but the queue stays clean. - Append to
~/.claude/second-nature/LOG.md:YYYY-MM-DD promote: installed (user|project).
4. Close
Confirm what was installed and where, with each skill's trigger word. Note that new skills are picked up by new sessions — in the current session the user can invoke them by name once the file exists.
Declined proposals stay in the queue unless the user says drop them (then archive to retired/, never delete).
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: mmusa
- Source: mmusa/second-nature
- 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.