jburns24/skill-name
template/SKILL.md
One-sentence description of what this skill does.
tools
Updated Apr 6, 2026
$ install --global
skillsauthnpx skillsauth add jburns24/skills skill-nameInstall 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 24, 2026, 8:38 PM1.8s1 file scanned
SKILL.md
- name:
- skill-name
- description:
- One-sentence description of what this skill does.
Skill Name
Brief overview of the skill's purpose.
When to Use
Describe the triggers or scenarios where this skill should be invoked.
Instructions
Step-by-step instructions for the agent to follow when this skill is activated.
- Step one
- Step two
- Step three
Examples
Provide one or two concrete examples of how the skill is used.
Related Skills
jburns24/prd-arena
data-ai
VerifiedTrustedCommunity
Orchestrate a competitive multi-agent PRD synthesis arena. Use when the user wants to synthesize, combine, or merge multiple PRDs into a single master PRD using competitive multi-agent workflow. Also triggers on: "prd arena", "prd competition", "compete PRDs", or when agents should independently draft competing PRDs from source materials and have them judged. Spawns 4 worker agents that create competing PRDs, then 3 manager agents that judge, debate, and synthesize into a final master PRD.md.
SKILL.mdUpdated Apr 16, 2026
jburns24/find-commit
testing
VerifiedTrustedCommunity
Searches git history for commits that contain generation-metadata blocks (created by the commit skill) and returns the plan intent, model, and unplanned changes for each match. Use this skill whenever an agent or user needs to understand why a change was made, trace a feature back to its plan, audit planned vs. actual changes, or find commits related to a topic. Triggers include "why was this changed", "find commits related to", "what plan drove this", "search commit history", "show me instrumented commits", "what was the intent behind", or any question about the reasoning or plan behind past changes.
SKILL.mdUpdated Apr 6, 2026
jburns24/commit
development
VerifiedTrustedCommunity
Creates a conventional-commit message with embedded generation metadata (model, plan file, unplanned changes) in an HTML comment after implementing a plan. Use this skill whenever the user says "commit this", "git commit", "make a commit", or asks to commit changes after completing a plan in plan mode.
SKILL.mdUpdated Apr 6, 2026
openclaw/taskflow
tools
VerifiedTrustedCommunity
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
357,764SKILL.mdUpdated Apr 10, 2026