n4m3z/AlignPrompt
skills/AlignPrompt/SKILL.md
Fix indentation, fence language tags, heading depth, and frontmatter fields to match forge conventions. USE WHEN an adopted community skill or any prompt-shaped document fails a forge convention check (indent, fence, heading, schema).
$ install --global
skillsauthnpx skillsauth add n4m3z/forge-core AlignPromptInstall 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 17, 2026, 8:08 AM4.6s1 file scanned
SKILL.md
- name:
- AlignPrompt
- description:
- Fix indentation, fence language tags, heading depth, and frontmatter fields to match forge conventions. USE WHEN an adopted community skill or any prompt-shaped document fails a forge convention check (indent, fence, heading, schema).
- version:
- 0.1.0
- allowed-tools:
- Read, Edit, Write
AlignPrompt
Bring a prompt-shaped document into forge convention without changing its meaning. Referenced by ForgeAdopt as the align transform.
What to fix
| Axis | Forge convention |
| ----------------- | ------------------------------------------------------------------------------ |
| Indentation | Four spaces. No tabs. Applies to markdown, YAML, TOML, JSON, code blocks. |
| Fence tags | Every fenced code block carries a language tag. Use sh, not bash. |
| Heading depth | Max depth 3. No skipped levels (no H1 to H3 without H2 between). |
| Heading style | One H1 per document, matching the skill name in PascalCase. |
| Frontmatter keys | name, description, version. Strip upstream fields forge does not use. |
| Skill name | PascalCase, two words, scope plus focus (for example SecurityBestPractices). |
| Table alignment | Pipes line up vertically; pad cells with spaces to the widest column. |
| Trailing newline | Every text file ends with a single \n. |
| Wikilinks / paths | Spaces literal, not URL-encoded. |
What to preserve
- The skill's actual instructions and workflow
- Body structure and section order unless a heading level is wrong
- Code block contents; only fix the fence tag, never the code inside
- Emphasis and voice, except where convention conflicts
Procedure
- Read the full document.
- Fix frontmatter first — it gates downstream checks.
- Walk the heading tree, flagging any skip or over-deep section.
- Sweep indentation; convert tabs to four spaces.
- Sweep fences; ensure every one has a language tag.
- Align tables column by column.
- Re-read; the content meaning must be unchanged.
Constraints
- Never rewrite content to fix alignment — only fix structure
- If an upstream skill legitimately needs H4 or H5, flag it as a content issue, do not silently demote
- Do not remove frontmatter fields the skill relies on for runtime behavior (
argument-hint,allowed-tools,hooks) - If the H1 title does not match the skill name, rename the file or rewrite the H1 — do not leave them divergent
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