pjt222/skill-name-here
skills/_template/SKILL.md
One to three sentences describing what this skill accomplishes, followed by key activation triggers. This field is the primary mechanism agents use to decide whether to activate the skill — it is read during discovery before the full body is loaded. Start with a verb. Include the most important "when to use" conditions inline. Max 1024 characters.
$ install --global
skillsauthnpx skillsauth add pjt222/agent-almanac skill-name-hereInstall 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 15, 2026, 9:27 AM6.9s1 file scanned
SKILL.md
- name:
- skill-name-here
- description:
- >
- license:
- MIT
- allowed-tools:
- Read Write Edit Bash Grep Glob
- author:
- Your Name
- version:
- 1.0
- domain:
- general # match the parent directory under skills/
- complexity:
- intermediate # one of: basic, intermediate, advanced
- language:
- multi # one of: R, TypeScript, Python, Docker, Rust, multi
- tags:
- tag1, tag2, tag3 # 3-6 lowercase tags for discovery; include the domain
Skill Title (Imperative Verb Form)
One paragraph: what this skill accomplishes and the value it provides.
When to Use
- Concrete scenario where an agent should activate this skill
- Another trigger condition
- A third use case
Inputs
- Required: Description of required input
- Required: Another required input
- Optional: Optional input with default (default: value)
Procedure
Step 1: Action Title
Context sentence explaining what this step accomplishes.
# Concrete command or code the agent can execute
example_command --flag value
Expected: What success looks like. Be specific -- file created, output matches pattern, command exits 0.
On failure: Recovery action. What to check, what to retry, when to abort.
Step 2: Next Action
Context for this step.
next_command
Expected: Specific success indicator.
On failure: Recovery action.
Validation
- [ ] First verification check
- [ ] Second verification check
- [ ] Third verification check
Common Pitfalls
- Pitfall name: Explanation and how to avoid it
- Another pitfall: Explanation and how to avoid it
Examples (Optional)
Short worked examples showing the skill in action. Keep inline examples brief; move extended or multi-variant examples to references/EXAMPLES.md.
Related Skills
related-skill-name-- how it relates to this skillanother-skill-- how it relates
Related Skills
pjt222/unleash-the-agents
testing
VerifiedTrustedCommunity
Launch all available agents in parallel waves for open-ended hypothesis generation on problems where the correct domain is unknown. Use when facing a cross-domain problem with no clear starting point, when single-agent approaches have stalled, or when diverse perspectives are more valuable than deep expertise. Produces a ranked hypothesis set with convergence analysis and adversarial refinement.
9SKILL.mdUpdated Apr 15, 2026
pjt222/test-cli-application
tools
VerifiedTrustedCommunity
Write integration tests for a Node.js CLI application using the built-in node:test module. Covers the exec helper pattern, output assertions, filesystem state verification, cleanup hooks, JSON output parsing, error case testing, and state restoration after destructive tests. Use when adding tests to an existing CLI, testing a new command, verifying adapter behavior across frameworks, or setting up CI for a CLI tool.
9SKILL.mdUpdated Apr 15, 2026
pjt222/screen-trademark
development
VerifiedTrustedCommunity
Screen a proposed trademark for conflicts and distinctiveness before filing. Covers trademark database searches (TMview, WIPO Global Brand Database, USPTO TESS), distinctiveness analysis using the Abercrombie spectrum, likelihood of confusion assessment using DuPont factors and EUIPO relative grounds, common law rights evaluation, and goods/services overlap analysis. Produces a conflict report with a risk matrix. Use before adopting a new brand name, logo, or slogan — distinct from patent prior art search, which uses different databases, legal frameworks, and analysis methods.
9SKILL.mdUpdated Apr 15, 2026
pjt222/scaffold-cli-command
tools
VerifiedTrustedCommunity
Scaffold a new CLI command using Commander.js with options, action handler, three output modes (human-readable, quiet, JSON), and optional ceremony variant. Covers command naming, option design, shared context patterns, error handling, and integration testing. Use when adding a command to an existing Commander.js CLI, designing a new CLI tool from scratch, or standardizing command structure across a multi-command CLI.
9SKILL.mdUpdated Apr 15, 2026