Best use case
missing-fields-skill is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Teams using missing-fields-skill should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/missing-fields-skill/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How missing-fields-skill Compares
| Feature / Agent | missing-fields-skill | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
This skill provides specific capabilities for your AI agent. See the About section for full details.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
This skill has no name or description fields in frontmatter.
Related Skills
malformed-skill
This YAML has a syntax error
test-skill
E2Eテスト用のスキル
another-skill
別のテスト用スキル
fixture-partial-skill
テスト用部分構成スキル
fixture-orchestration-skill
テスト用オーケストレーションスキル
fixture-minimal-skill
テスト用最小構成スキル
fixture-invalid-skill
This is invalid: because of unquoted colon
fixture-invalid-schema-skill
Skill with invalid JSON schema for testing
Invalid_Name_With_Uppercase
Skill with invalid non-kebab-case name
fixture-forbidden-files-skill
Skill with forbidden files for testing
fixture-empty-agents-skill
Skill with empty agents directory for testing
fixture-complete-skill
テスト用完全構成スキル - skill-creator出力検証用フィクスチャ。 全ディレクトリ（agents/, references/, scripts/, assets/, schemas/）を含む完全な構造。 Anchors: * Clean Code (Robert C. Martin) / 適用: コード品質 / 目的: テスト可能な構造設計 * Test-Driven Development (Kent Beck) / 適用: テスト駆動 / 目的: フィクスチャ検証 Trigger: fixture validation, complete skill test, skill-creator output verification