go-go-golems/internal/templates/embedded/_guidelines
internal/templates/embedded/_guidelines/SKILL.md
# Guidelines: Skill Documents ## Purpose Skills are **disciplined workflows** written as documents (`DocType: skill`) that teach LLMs (and humans) *how to work*, not just what exists. A good skill turns “best practice” into a repeatable, enforceable process. Skills are meant to be discoverable via: - `docmgr skill list` (filter by topics, file/dir, ticket) - `docmgr skill show <query>` (load and apply a skill) ## Required Elements - **Frontmatter contract** - `DocType: skill` - `Title`: U
$ install --global
skillsauthnpx skillsauth add go-go-golems/docmgr internal/templates/embedded/_guidelinesInstall 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 5, 2026, 1:58 PM10.1s11 files scanned
SKILL.md
Guidelines: Skill Documents
Purpose
Skills are disciplined workflows written as documents (DocType: skill) that teach LLMs (and humans) how to work, not just what exists. A good skill turns “best practice” into a repeatable, enforceable process.
Skills are meant to be discoverable via:
docmgr skill list(filter by topics, file/dir, ticket)docmgr skill show <query>(load and apply a skill)
Required Elements
- Frontmatter contract
DocType: skillTitle: Use the conventionSkill: <Name>(recommended)Topics: Choose topics that match how developers will search (e.g.tdd,debugging,docs)WhatFor: 2–5 sentences describing the outcome this workflow ensuresWhenToUse: Clear trigger conditions (“Use when …”)
- Body
- Overview: 2–5 sentences (why it matters; what it enforces)
- When to Use: Concrete triggers + examples
- Process: Step-by-step actions (copy/paste friendly commands where possible)
- Verification: Checklist to prevent “I think I’m done” drift
Best Practices
- Be explicit: Use strong modal language (“MUST”, “NEVER”, “STOP”) where appropriate.
- Optimize for discovery: Ensure
Topics,WhatFor, andWhenToUsecontain the words people will actually search for. - Prefer commands over prose: If there’s a canonical command sequence, include it as a
bashblock. - Make validation unskippable: Add a checklist and expected success criteria (tests/linters/scenario suites).
References
pkg/doc/how-to-write-skills.md— Full guidance on writing and enforcing skillspkg/doc/using-skills.md— How to discover and load skills via CLI
Related Skills
go-go-golems/ttmp/_templates
documentation
VerifiedTrustedCommunity
--- Title: "Skill: [Name]" Ticket: [TICKET-ID] DocType: skill Status: active Topics: [] WhatFor: "Brief description of what this skill is for" WhenToUse: "Brief description of when to use this skill" RelatedFiles: [] Intent: long-term Owners: [] ExternalSources: [] Summary: "" LastUpdated: [TIMESTAMP] --- # Skill: [Name] ## Overview [Brief overview of the skill] ## What This Skill Is For [Detailed description of what this skill is for] ## When To Use This Skill [Detailed description of wh
13SKILL.mdUpdated May 30, 2026
go-go-golems/ttmp/_guidelines
documentation
VerifiedTrustedCommunity
# Guidelines: Skill Plans ## Purpose Skills are packaged workflows defined by a `skill.yaml` plan and an exported `SKILL.md` body. The plan tells docmgr what to package (files, help output), while the body teaches LLMs (and humans) *how to work*, not just what exists. Skills are meant to be discoverable via: - `docmgr skill list` (filter by topics, file/dir, ticket) - `docmgr skill show <query>` (load and apply a skill plan) ## Required Elements - **skill.yaml metadata** - `skill.name`: low
13SKILL.mdUpdated May 30, 2026
go-go-golems/internal/templates/embedded/_templates
documentation
VerifiedTrustedCommunity
--- Title: {{TITLE}} Ticket: {{TICKET}} Status: draft Topics: {{TOPICS}} DocType: skill Intent: long-term Owners: {{OWNERS}} RelatedFiles: [] ExternalSources: [] Summary: > {{SUMMARY}} LastUpdated: {{DATE}} WhatFor: > <!-- 2–5 sentences: what outcome does this workflow enforce? --> WhenToUse: > <!-- Trigger conditions: "Use when ..." --> --- # {{TITLE}} ## Overview <!-- 2–5 sentences: why this skill matters and what it enforces --> ## When to Use <!-- concrete triggers + examples -->
13SKILL.mdUpdated May 30, 2026
openclaw/openclaw-secret-scanning-maintainer
development
VerifiedTrustedCommunity
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
357,764SKILL.mdUpdated Apr 15, 2026