axiomantic/opportunity-awareness
skills/opportunity-awareness/SKILL.md
Triggers after completing substantive work (finishing a todo, returning from subagent, applying non-obvious convention, receiving user correction). Also: 'what should we capture', 'reusable pattern', 'should this be a skill', 'AGENTS.md update', 'knowledge gap'. Behavioral skill loaded at natural pause points.
$ install --global
skillsauthnpx skillsauth add axiomantic/spellbook opportunity-awarenessInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 20, 2026, 3:20 PM1.9s1 file scanned
SKILL.md
- name:
- opportunity-awareness
- description:
- Triggers after completing substantive work (finishing a todo, returning from subagent, applying non-obvious convention, receiving user correction). Also: 'what should we capture', 'reusable pattern', 'should this be a skill', 'AGENTS.md update', 'knowledge gap'. Behavioral skill loaded at natural pause points.
<analysis>
Behavioral nudge to capture reusable patterns, skills, and project knowledge at natural pause points after substantive work.
</analysis>
<reflection>
Did I surface an observation without interrupting urgent work, and was the suggestion specific enough to act on?
</reflection>
Opportunity Awareness
Type: Discipline (behavioral nudge)
Invariant Principles
- Pause Points Only - Surface observations after phases complete or at "what's next" moments, never mid-task or during urgent work.
- Specificity Over Volume - One actionable suggestion beats three vague ones; name the exact artifact type and why it matters.
- One-Off Work Stays One-Off - Do not suggest capturing obviously non-reusable tasks; the signal-to-noise ratio of suggestions matters.
After completing substantive work, consider whether what just happened would be valuable as a reusable artifact or project knowledge. Surface observations at natural pause points: after a phase completes, when presenting results, or when the user asks "what's next."
Do not suggest artifacts for obviously one-off tasks. Do not interrupt urgent work.
Artifact Candidates
Mention briefly, offer to draft via background agent:
| Type | Signal | |------|--------| | Skill | Non-obvious technique or undocumented convention that future sessions need. | | Command | Multi-step procedure with a clear trigger, identical every time. | | Agent | Self-contained task with specific tool access and persona, delegatable. |
If the user says yes, dispatch a background agent with the appropriate writing skill (e.g., writing-skills, writing-commands).
Project Knowledge Candidates
Offer to add to AGENTS.md when:
- You searched for build/test/run info that was undocumented
- You made a mistake from an undocumented convention (especially after user correction)
- You discovered a non-obvious dependency or read 5+ files for a one-sentence pattern
- The user explained something not written anywhere
Subagent Observations
Subagents should append a ## Skill Observations section to output when they notice reusable patterns. Check for this section and relay suggestions to the user.
Related Skills
axiomantic/writing-skills
testing
VerifiedTrustedCommunity
Use when creating new skills, editing existing skills, or verifying skills work before deployment. Triggers: 'write a skill', 'new skill', 'create a skill', 'skill doesn't work', 'skill isn't firing', 'edit skill', 'skill quality'. NOT for: general prompt improvement (use instruction-engineering) or command creation (use writing-commands).
5SKILL.mdUpdated Apr 3, 2026
axiomantic/writing-plans
development
VerifiedTrustedCommunity
Use when you have a spec, design doc, or requirements and need a detailed implementation plan before coding. Triggers: 'write a plan', 'create implementation plan', 'plan this out', 'break this down into steps', 'convert design to tasks', 'implementation order'. Also invoked by develop during planning. NOT for: reviewing existing plans (use reviewing-impl-plans).
5SKILL.mdUpdated Apr 3, 2026
axiomantic/writing-commands
testing
VerifiedTrustedCommunity
Use when creating new commands, editing existing commands, or reviewing command quality. Triggers: 'write command', 'new command', 'create a command', 'review command', 'fix command', 'command doesn't work', 'add a slash command'. NOT for: skill creation (use writing-skills).
5SKILL.mdUpdated Apr 3, 2026
axiomantic/verifying-hunches
development
VerifiedTrustedCommunity
Use when about to claim discovery during debugging. Triggers: "I found", "this is the issue", "I think I see", "looks like the problem", "that's why", "the bug is", "root cause", "culprit", "smoking gun", "aha", "got it", "here's what's happening", "the reason is", "causing the", "explains why", "mystery solved", "figured it out", "the fix is", "should fix", "this will fix". Also invoked by debugging, scientific-debugging, systematic-debugging before any root cause claim.
5SKILL.mdUpdated Apr 3, 2026