ivy/gfm
home/dot_claude/skills/gfm/SKILL.md
Use when writing or reviewing GitHub-flavored Markdown (README, issues, PRs, docs)
$ install --global
skillsauthnpx skillsauth add ivy/dotfiles gfmInstall 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 16, 2026, 11:00 AM12.2s1 file scanned
SKILL.md
- name:
- gfm
- description:
- Use when writing or reviewing GitHub-flavored Markdown (README, issues, PRs, docs)
- argument-hint:
- [file | topic | review]
GitHub-Flavored Markdown
Arguments
$ARGUMENTS
Instructions
Parse arguments to determine task:
- File path → Write/edit markdown file
- "review" → Audit existing markdown for GFM best practices
- Topic/description → Draft markdown content
Writing Guidelines
Structure:
- Use heading hierarchy (
#through######)—GitHub auto-generates TOC for 2+ headings - Prefer ATX headings (
#) over Setext (===) - One blank line before headings
Text styling:
| Style | Syntax |
|-------|--------|
| Bold | **text** |
| Italic | _text_ |
| Bold+italic | ***text*** |
| Strikethrough | ~~text~~ |
| Code | `code` |
| Subscript | <sub>x</sub> |
| Superscript | <sup>2</sup> |
Code blocks:
```language
code here
```
Lists:
- Unordered: use
-consistently - Ordered:
1.,2., etc. - Task lists:
- [ ]incomplete,- [x]complete - Nest by aligning under parent text
Links:
- Inline:
[text](url) - Section anchors:
[text](#heading-name)(lowercase, hyphens, no punctuation) - Relative paths for repo files:
docs/CONTRIBUTING.md
Images:  — always include alt text
Alerts (callouts):
> [!NOTE]
> Useful information
> [!TIP]
> Helpful advice
> [!IMPORTANT]
> Essential info
> [!WARNING]
> Urgent attention
> [!CAUTION]
> Risk warning
Footnotes:
Text with footnote[^1].
[^1]: Footnote content.
Color swatches: `#FF5733`, `rgb(255,87,51)`, `hsl(11,100%,60%)`
Review Checklist
When reviewing markdown:
- [ ] Heading hierarchy is logical (no skipped levels)
- [ ] Code blocks specify language for syntax highlighting
- [ ] Links use relative paths for repo files
- [ ] Images have meaningful alt text
- [ ] Task lists use proper syntax
- [ ] Alerts use correct
> [!TYPE]format - [ ] No trailing whitespace except intentional line breaks
- [ ] Tables are properly aligned
Examples
/gfm README.md → Edit/create README
/gfm review docs/ → Audit markdown files in docs/
/gfm API documentation → Draft API docs content
/gfm changelog entry → Write changelog in GFM style
Related Skills
ivy/handoff
tools
VerifiedTrustedCommunity
Write a handoff brief summarizing the current conversation so a fresh agent can pick up the work. Writes to a file if given, otherwise copies to the clipboard.
7SKILL.mdUpdated Jun 4, 2026
ivy/mob
data-ai
VerifiedTrustedCommunity
Use when the user wants to set, change, or clear git commit co-authors for pair or mob programming.
7SKILL.mdUpdated Apr 16, 2026
ivy/hk
tools
VerifiedTrustedCommunity
Use when bootstrapping hk pre-commit hooks for a project.
7SKILL.mdUpdated Apr 16, 2026
ivy/grill-me
testing
VerifiedTrustedCommunity
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
7SKILL.mdUpdated Apr 16, 2026