n4m3z/BuildSkill
skills/BuildSkill/SKILL.md
Create and validate skills for forge modules. USE WHEN create skill, new skill, write skill, validate skill, check skill, skill structure, skill conventions.
$ install --global
skillsauthnpx skillsauth add n4m3z/forge-core BuildSkillInstall 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: May 28, 2026, 6:16 AM46.0s9 files scanned
SKILL.md
- name:
- BuildSkill
- version:
- 0.1.0
- description:
- Create and validate skills for forge modules. USE WHEN create skill, new skill, write skill, validate skill, check skill, skill structure, skill conventions.
BuildSkill
Create and validate skills following forge conventions. Skills are markdown files (SKILL.md) with YAML frontmatter that teach AI coding tools new capabilities. Load only the companion relevant to the current task.
Workflow Routing
| Workflow | Trigger | Companion | | ------------ | ------------------------------------------------ | ------------------------------------------------- | | Create | "create a skill", "new skill", "write a skill" | @CreateWorkflow.md | | Validate | "validate skill", "check skill structure" | @ValidateWorkflow.md |
Topics
| Topic | Companion |
| ----------------------------------------------------------- | -------------------------------------------------------- |
| SKILL.md structure, frontmatter, body layout, naming | @SkillStructure.md |
| Multi-provider routing via defaults.yaml | @MultiProviderRouting.md |
| Wrapping a CLI tool in a skill | @CliToolIntegration.md |
| Platform-agnostic writing — no placeholders or / prefix | @PlatformAgnostic.md |
| When to author a per-skill INSTALL.md | @SkillInstallation.md |
Red Flags
| Thought | Reality |
| -------------------------------------------------------- | ------------------------------------------------------------------------------------ |
| "Put argument-hint in SKILL.md frontmatter" | Obsidian Linter reformats frontmatter. Provider-specific fields go in SKILL.yaml. |
| "Use /SkillName inside a skill body" | Slashes are user-facing invocation syntax, not internal references. |
| "Skip the USE WHEN clause" | Claude uses it to route. Missing trigger = skill never fires. |
| "Leave a stub section as a placeholder" | Skill bodies are plain prose. Delete empty sections, don't scaffold them. |
| "Inline every example in the SKILL.md" | SKILL.md should stay slim. Move static reference material to companion files. |
| "Skill directory can have any name" | Directory name must match the name: frontmatter field exactly. |
Constraints
- Every skill MUST have
name:anddescription:in frontmatter - Description MUST include
USE WHENtrigger phrases - PascalCase for multi-word skill names, natural case for single words
- Skill directory name must match the
name:field - Prefer one SKILL.md per skill — extract reference material into companion files when body exceeds ~150 lines or contains dense static data
Sources
- https://code.claude.com/docs/en/skills
- https://github.com/anthropics/skills
Related Skills
n4m3z/Wtf
development
VerifiedTrustedCommunity
Reactive correction and root-cause fix. USE WHEN something went wrong, user is frustrated, demands a correction, says wtf, what the hell, why did you, that's wrong, this is broken, no not that, stop. Executes the immediate fix, then hunts the upstream artifact that caused it and creates a corrective change.
4SKILL.mdUpdated May 28, 2026
n4m3z/ResearchTopic
development
VerifiedTrustedCommunity
Decompose a research question into sub-queries, spawn parallel WebResearcher agents per angle, synthesize findings with citations and explicit confidence. USE WHEN the user asks to research, investigate, look online, look up, dig into, find sources, gather evidence, or survey what's known about a topic. Single-pass; for multi-round adversarial research use ResearchCouncil in forge-council.
4SKILL.mdUpdated May 27, 2026
n4m3z/WriteDocs
tools
VerifiedTrustedCommunity
Author project documentation that future humans (and AI sessions) actually read. Covers TLDRs for tools, READMEs, runbooks, journals. USE WHEN write documentation, create tldr, tool one-pager, document a cli, write readme, runbook, journal entry, capture knowledge about a tool, distill a session into reusable notes.
4SKILL.mdUpdated May 25, 2026
n4m3z/StagedReview
development
VerifiedTrustedCommunity
Review your own staged changes via a code-review TUI before triggering a commit. USE WHEN about to commit, walking through your own staged diff, self-reviewing before approval, tuicr, revdiff, git diff cached.
4SKILL.mdUpdated May 25, 2026