feature-flags-architect

From the files and frontmatter at commit 7f92eda. This is how much a skill can do, not whether it is risky.

• Runs shell commands

  Its instructions or files give the agent commands to run on your computer.

• Bundles scripts

  The folder holds code files the agent may run.

Pattern check: nothing flagged · commit 7f92eda · 3 Nov 2026

We checked every text file in this skill, at commit 7f92eda on 3 Nov 2026, against 45 published patterns such as download-and-run commands, hidden text and credential access. We don't run the skill, we don't read the web pages it points to, and we can't judge everything its instructions might lead an agent to do. In published tests, pattern checks like this one missed most malicious skills. Read the skill before you install it — especially anything it asks you to download or run.

How the check worksReport an incorrect finding

Each agent reads SKILL.md a little differently. We check the file against each one's published rules; we don't run the skill in any agent.

• Agent Skills specPasses with warnings

  The open format from agentskills.io, held to the strictest version of each rule among the agents we check.

  • Warning

    The frontmatter uses [ ] or { } values. Most agents accept them, but the spec's validator (skills-ref) rejects the file. F4

    Fix: Write lists as "- item" lines and maps as indented key: value lines, without anchors or tags.

  • Warning

    Fields outside the spec: context (read by Claude Code and VS Code). Uploads to the Claude apps and API, and the spec's validator, reject the file; most agents ignore these fields. O1

    Fix: Delete them for a portable skill, or keep them if you only target the agents that read them.

  • Warning

    metadata values should be text; tags (a list) and compatible_tools (a list) are not. The spec's validator turns them into text; other readers may not. O4

    Fix: Quote each value, for example version: "1.0".

  • Note

    Reference files over 100 lines with no table of contents at the top: references/flag_lifecycle.md (172 lines), references/flag_taxonomy.md (126 lines), references/provider_comparison.md (160 lines) and references/rollout_strategies.md (141 lines). B5

    Fix: Add a short list of the sections at the top of each.

• Claude CodePasses

  Claude Code reads its own extra fields, ignores unknown ones, and still loads a skill whose frontmatter is broken, without its fields.

  • Note

    Reference files over 100 lines with no table of contents at the top: references/flag_lifecycle.md (172 lines), references/flag_taxonomy.md (126 lines), references/provider_comparison.md (160 lines) and references/rollout_strategies.md (141 lines). B5

    Fix: Add a short list of the sections at the top of each.

• Claude apps & API uploadFails

  Uploading to claude.ai or the Claude API, or packaging with Anthropic's script, accepts only the six spec fields and stops on anything else.

  • Error

    Upload and packaging fail on fields outside the spec: context. O1

    Fix: Delete them, and keep your own data under metadata as text values.

  • Note

    The description is 240 characters. The claude.ai Help Center says 200 at most, though Anthropic's API docs and validator allow 1,024. D4

    Fix: If the claude.ai upload refuses it, trim the description to 200 characters.

  • Note

    metadata values should be text; tags (a list) and compatible_tools (a list) are not. The spec defines metadata as text to text. O4

    Fix: Quote each value, for example version: "1.0".

  • Note

    Reference files over 100 lines with no table of contents at the top: references/flag_lifecycle.md (172 lines), references/flag_taxonomy.md (126 lines), references/provider_comparison.md (160 lines) and references/rollout_strategies.md (141 lines). B5

    Fix: Add a short list of the sections at the top of each.

• OpenAI (Codex & API)Passes with warnings

  Codex finds SKILL.md by its exact name and needs a description; OpenAI's Skills API checks the frontmatter against the spec and caps uploads.

  • Warning

    Fields outside the spec: context. Codex ignores them; OpenAI doesn't say whether its upload accepts them. O1

    Fix: Delete them, or move your own data under metadata as text values.

  • Warning

    metadata values should be text; tags (a list) and compatible_tools (a list) are not. OpenAI's upload follows the spec's text-to-text rule. O4

    Fix: Quote each value, for example version: "1.0".

• VS Code & CopilotPasses

9 files