ワンクリックでManusで任意のスキルを実行

始める

gfm

スター0

フォーク0

更新日2026年5月12日 15:15

Use when writing or reviewing GitHub-flavored Markdown (README, issues, PRs, docs)

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

meaganewaller

meaganewaller/dotfiles

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

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: ![alt text](url) — 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

このリポジトリの他の Skills

同じリポジトリ

agent-self-evaluation

meaganewaller/dotfiles

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.

2026-07-130

install-tool

meaganewaller/dotfiles

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.

2026-06-100

meaganewaller/dotfiles

Use when creating a pull request. Opens PR in browser for review.

2026-06-100

agent-browser

meaganewaller/dotfiles

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.

2026-05-280

apple-notes

meaganewaller/dotfiles

Create, view, edit, delete, search, move, or export Apple Notes via the memo CLI on macOS.

2026-05-280

babysit-pr

meaganewaller/dotfiles

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

2026-05-280

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: ![alt text](url) — 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