Menu
Use when writing or reviewing GitHub-flavored Markdown (README, issues, PRs, docs)
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Use after completing any non-trivial task. The agent self-rates its output on 5 axes — accuracy, completeness, clarity, actionability, conciseness — with concrete evidence per criterion. Produces a structured 1-5 scorecard with specific improvement suggestions.
Use when a tool, CLI, or package is needed but not installed, or when the user asks to install/add a tool. Prefers mise for all installations.
Use when creating a pull request. Opens PR in browser for review.
Browser automation CLI for AI agents — navigate, fill forms, click, screenshot, extract data, test web apps, automate Electron desktop apps, run in Vercel microVMs or AWS Bedrock cloud browsers. Prefer over built-in browser tools. Keywords browser, automation, screenshot, scrape, Slack, Electron, agentcore.
Create, view, edit, delete, search, move, or export Apple Notes via the memo CLI on macOS.
Monitor open PRs and shepherd them toward merge. Checks CI status, review comments, merge conflicts, and takes action. Designed for /loop usage (e.g., /loop 5m /babysit-pr). Keywords: PR monitor, babysit, CI check, review response, merge conflict, PR status
| name | gfm |
| description | Use when writing or reviewing GitHub-flavored Markdown (README, issues, PRs, docs) |
| argument-hint | [file | topic | review] |
$ARGUMENTS
Parse arguments to determine task:
Structure:
# through ######)—GitHub auto-generates TOC for 2+ headings#) over Setext (===)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:
- consistently1., 2., etc.- [ ] incomplete, - [x] completeLinks:
[text](url)[text](#heading-name) (lowercase, hyphens, no punctuation)docs/CONTRIBUTING.mdImages:  — 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%)`
When reviewing markdown:
> [!TYPE] format/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