Skip to content

rse/ase / plugin/skills/ase-sync-export

ase-sync-export

Verified

Export the SpecBook-based specification (SPEC) into ready-to-consume renderings like HTML, PDF, normalized Markdown, or JSON. Use when the user wants to "export", "render", or "materialize" the specification.

FileKindSize
SKILL.mdskill md5.1 KB
help.mdmarkdown2.7 KB
---
name: ase-sync-export
argument-hint: "[--help|-h] [--output|-o <output>[,...]]"
description: >
    Export the SpecBook-based specification (SPEC) into ready-to-consume
    renderings like HTML, PDF, normalized Markdown, or JSON. Use when the
    user wants to "export", "render", or "materialize" the specification.
user-invocable: true
disable-model-invocation: false
effort: xhigh
---

@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
@${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
@${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md

<purpose name="ase-sync-export">
Export Specification into Rendered Files
</purpose>

<expand name="getopt"
    arg1="ase-sync-export"
    arg2="--output|-o=">
    $ARGUMENTS
</expand>

<objective>
*Export* the `SPEC` artifact set -- the SpecBook-based specification --
into the requested output files, by validating the specification and
rendering it through the SpecBook export.
</objective>

@${CLAUDE_SKILL_DIR}/../../meta/ase-format-meta.md

Procedure
---------

<flow>

1.  <step id="STEP 1: Determine Outputs">

    1.  Parse <getopt-option-output/> as the comma-separated <outputs/>
        list of `[<format>:]<file>` entries, with <format/> one of
        `json`, `json5`, `yaml`, `toon`, `html`, `pdf`, or `md`, and
        <file/> a project-relative output file path. Trim every parsed
        entry. Do not output anything.

    2.  <if condition="<outputs/> is empty">

        Determine the default output by calling the
        `ase_artifact_name(filename: "index.html", kind: "spec")` tool
        of the `ase` MCP server and set <outputs/> to the single entry
        of its returned `name`. Do not output anything.

        </if>

    3.  If any entry in <outputs/> is `-` (the standard output sentinel),
        only output the following <template/> and then immediately *STOP*
        processing the entire current skill:

        <template>
        ⧉ **ASE**: ☻ skill: **ase-sync-export**, ▶ ERROR: output `-` is not supported -- give an output file
        </template>

    4.  Report the resolved outputs with the following <template/>:

        <template>
        <ase-tpl-bullet-signal/> **OUTPUTS**: <outputs/>
        </template>

    </step>

2.  <step id="STEP 2: Validate Specification">

    1.  Call the `ase_specbook_lint()` tool of the `ase` MCP server
        *once* and read its returned `diagnostics` array of `{ file,
        line, column, severity, message }` objects, reduced to those
        entries whose <severity/> is `error`, as only those make the
        export fail. Do not output anything.

    2.  <if condition="<diagnostics/> is not empty">

        Only output the following <template/> (listing one bullet line
        per diagnostic), give the closing hint by expanding the
        `<ase-tpl-hint/>` below it, and then immediately *STOP*
        processing the entire current skill:

        <template>
        ⧉ **ASE**: ☻ skill: **ase-sync-export**, ▶ ERROR: specification invalid -- nothing exported

        -   `<file/>:<line/>:<column/>`: <message/>
        [...]
        </template>

        <ase-tpl-hint level="minimal">
        Fix the reported diagnostics in the `SPEC` artifacts (e.g. via `/ase-sync-reconcile -t SPEC`), then re-run this skill.
        </ase-tpl-hint>

        </if>

    </step>

3.  <step id="STEP 3: Export Specification">

    1.  For *each* <output/> in <outputs/>, call the
        `ase_specbook_export(output: "<output/>")` tool of the `ase` MCP
        server, which infers the format from the `[<format>:]<file>`
        entry, writes the rendering to the file, and returns a
        confirmation `text` carrying the written byte size plus a
        `notices` array of environment notices. Set <notices/> to the
        *distinct* notices of all calls. Do not output anything.

    2.  Report the exported files with the following <template/>,
        listing one bullet line per written file (with <file/> its
        project-relative path and <note/> the format and the byte size):

        <template>
        <ase-tpl-bullet-signal/> **EXPORTED SPECIFICATION**:

        -   `<file/>`: <note/>
        [...]
        </template>

    3.  <if condition="<notices/> is not empty">

        Report the environment notices *verbatim* with the following
        <template/>, listing one bullet line per notice:

        <template>
        <ase-tpl-bullet-signal/> **ENVIRONMENT NOTICES**:

        -   <notice/>
        [...]
        </template>

        </if>

    4.  Finally, give the closing hints by expanding the following
        (which, depending on the configured <ase-guidance-level/>, may
        each expand into nothing and hence emit no output at all):

        <ase-tpl-hint level="normal">
        Exports are *derived* and go stale as the specification drifts -- use `/ase-sync-reconcile` to align the artifacts first, then re-run this skill.
        </ase-tpl-hint>

        <ase-tpl-hint level="verbose">
        Use `/ase-sync-export --output` with a comma-separated list of `[<format>:]<file>` entries to export several renderings at once (e.g. `-o docs/spec.html,docs/spec.pdf`).
        </ase-tpl-hint>

    </step>

</flow>
canvas-designanthropics/skillsCreate beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
docxanthropics/skillsUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
pdfanthropics/skillsUse this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
pptxanthropics/skillsUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill.Stars: 198kUpdated Claude CodeCodexVerifiedInstall