check-skill-formatting
Checks skill files for formatting violations — preprocessing patterns, placeholder conventions, and frontmatter. Use when validating skills, checking formatting, or when check formatting, lint skills, or skill quality are mentioned.
ソース情報
- リポジトリ
- outfitter-dev/outfitter
- ソースの最終更新活動
- 2026年2月25日 16:13
- 検出された SKILL.md の言語
- 英語
- スター
- 6
- フォーク
- 1
インストール方法
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
ソースファイルを確認
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
ファイルエクスプローラー
2 ファイルSKILL.md を表示中
SKILL.md
ソースの指示 · 読み取り専用プレビュー- name
- check-skill-formatting
- description
- Checks skill files for formatting violations — preprocessing patterns, placeholder conventions, and frontmatter. Use when validating skills, checking formatting, or when check formatting, lint skills, or skill quality are mentioned.
- user-invocable
- true
- allowed-tools
- Skill, Bash, Read, Glob, Grep
- argument-hint
- [path]
# Check Skill Formatting
Validate skill files against formatting conventions. Catches preprocessing hazards, placeholder violations, and frontmatter issues.
## Steps
1. Load the `/skillcheck` skill (runs preprocessing linter)
2. Run the placeholder linter to find `[string]` patterns that should use `{ string }` convention
3. Run the fence linter to find bare code fences and nesting issues
4. Run the relative paths linter to find `../` references that should use `${CLAUDE_PLUGIN_ROOT}`
5. Review findings and fix violations
## Placeholder Linter
Scan markdown files for `[string]` patterns that aren't markdown links or file references:
```bash
bun .claude/skills/check-skill-formatting/scripts/lint-placeholders.ts ${ARGUMENTS:-plugins/}
```
### What it catches
Instructional placeholders using brackets instead of braces:
| Found | Expected |
| --------------------------------- | ----------------------------------- |
| `[Complete AWS-specific content]` | `{ complete AWS-specific content }` |
| `[Details follow...]` | `{ details follow }` |
| `[Section content]` | `{ section content }` |
### What it skips
- Markdown links: `[text](url)` or `[text](#anchor)`
- File references: `[file.md]`, `[config.json]`
- Checkboxes: `[x]`, `[ ]`, `[-]`
- GitHub admonitions: `[!NOTE]`, `[!WARNING]`
- Code fences and HTML comments
- All-caps tokens under 12 chars: `[REDACTED]`, `[TIME]`
## Fence Linter
Scan markdown files for code fence issues — bare fences without language specifiers and broken nesting:
```bash
bun plugins/fieldguides/scripts/lint-fences.ts ${ARGUMENTS:-plugins/}
```
### What it catches
- **Bare fences**: Opening ` ``` ` without a language (suggests one based on content heuristics)
- **Broken nesting**: Inner fence with same backtick count as outer fence (use ` ` ```` for outer)
### Fix patterns
| Issue | Fix |
| ---------------------------------- | ---------------------------- |
| ` ``` ` with TypeScript content | ` ```typescript ` |
| ` ``` ` with shell commands | ` ```bash ` |
| ` ``` ` with plain text | ` ```text ` |
| Inner ` ``` ` inside outer ` ``` ` | Use ` ` ```` for outer fence |
## Relative Paths Linter
Scan markdown files for `../` path references that should use `${CLAUDE_PLUGIN_ROOT}`:
```bash
bun plugins/fieldguides/scripts/lint-relative-paths.ts ${ARGUMENTS:-plugins/}
```
### What it catches
- **Markdown links**: `[text](../other-skill/SKILL.md)` with relative targets
- **Bare paths**: `../SECURITY.md` references in prose
### Fix patterns
| Issue | Fix |
| --------------------------------- | ---------------------------------------------------------- |
| `[link](../skill-name/SKILL.md)` | `[link](${CLAUDE_PLUGIN_ROOT}/skills/skill-name/SKILL.md)` |
| `[link](../patterns/handler.md)` | `[link](${CLAUDE_PLUGIN_ROOT}/shared/patterns/handler.md)` |
| `../EXTERNAL.md` (outside plugin) | Remove link or reference by name |
GitHubで見る