Skip to content

Setup can generate skill frontmatter as markdown table instead of YAML #2

Description

@oreganoflakesgit

Problem

/setup may emit some generated skill frontmatter as markdown table rows instead of YAML.

Example:

| name | description | user-invocable | allowed-tools | context | model |
|------|-------------|----------------|---------------|---------|-------|
| research | Extract structured knowledge from source material. Comprehensive extraction is the default — every insight that serves the domain gets extracted. | true | Read, Write, Grep, Glob, mcp__qmd__vsearch | fork | opus |

Expected:

---
name: learn
description: Research a topic and grow your knowledge graph. Uses Exa deep researcher, web search, or basic search to investigate topics, files results with full provenance, and chains to processing pipeline. Triggers on "/learn", "/learn [topic]", "research this", "find out about".
version: "1.0"
generated_from: "arscontexta-v1.6"
user-invocable: true
context: fork
model: opus
allowed-tools: Read, Write, Edit, Grep, Glob, Bash, mcp__exa__web_search_exa, mcp__exa__deep_researcher_start, mcp__exa__deep_researcher_check, WebSearch
---

Impact

Malformed skill metadata in .claude/skills/*/SKILL.md breaks skill invocation.

Proposed fix

  • add a setup-focused frontmatter validator script
  • run it during setup validation
  • document a QA milestone for manual/CI verification"

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions