メニュー
Use this skill to export and open A2A agent task outputs — "export the task results", "convert the task output to HTML", or work with the structured artifacts produced by an A2A agent task run.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Show the user the agent's work on a research project and save iterations on the user's behalf. Scaffold rendering and deploy infrastructure (Quarto today, GitHub Pages, dev container), show the rendered output, save iterations. Doesn't handle research execution (use `asta-flows`).
Install or update the `asta` CLI to the version pinned by this plugin. Invoke whenever `asta` is not on PATH (e.g. `command not found` for `asta`) or when a subcommand/flag appears missing — that signals a stale install needing an update.
Converse with the user to identify the next most productive units of work for the current project, and record them in project.md under Pending Work. Use when the user wants to plan what to work on next, or when there is no project.md yet.
Execute the approved plan in work/<slug>/README.md (status ready), write outputs into work/<slug>/data/, record what happened in the Results section, then hand off to review-work. Use when there is a ready work item.
Write a detailed, executable plan for a single unit of work, then get it approved by review-plan. Updates work/<slug>/README.md with concrete instructions and sets status to ready (or needs-input if review repeatedly rejects).
Critic skill. Given a plan in work/<slug>/README.md (status pending-review), check that the steps are concrete, the tools are appropriate, and the plan is realistic. Write a verdict and feedback back into the README.
| name | artifacts |
| description | Use this skill to export and open A2A agent task outputs — "export the task results", "convert the task output to HTML", or work with the structured artifacts produced by an A2A agent task run. |
| allowed-tools | Bash(asta * task *) Bash(asta artifacts *) Bash(asta documents *) Bash(open *) |
Artifacts are the structured outputs produced by A2A agents. They accumulate in the artifacts[] field of the task response.
# 1. Dump task result
TASK_DIR=$(mktemp -d)
asta <agent> task "<TASK_ID>" > "$TASK_DIR/task.json"
# 2. Export (caller decides output dir and format)
asta artifacts --input "$TASK_DIR" --output "$OUT_DIR" --format md
Produces per-artifact files organized by subtype, plus index.md, references.bib, and manifest.json.
Works on partial task data too — useful for previewing mid-run.
--format md — markdown, one .md per artifact. Cross-artifact links use relative .md paths. Best for LLM consumption, version control, and indexing into asta-documents.--format html — self-contained HTML with index.html. Open with open "$OUT_DIR/index.html". Best for reading or sharing.When another skill hands off to this one to export a run, default to writing under:
.asta/<invoking-skill>/<slug>/
Where <slug> is YYYY-MM-DD-<short-query-slug> — date-first for
chronological ordering, short-slug derived from the primary input (query,
topic, etc.). Register the exported artifacts with asta-documents into a
single per-skill aggregate index at .asta/<invoking-skill>/index.yaml so
consumers can search across all runs.
Example (theorizer run):
.asta/generate-theories/2026-04-17-media-polarization/ # per-run outputs
.asta/generate-theories/index.yaml # aggregate index
After export, read manifest.json and register each entry with asta documents add. Each manifest entry has: name, description, filename, mime_type, and optionally subtype and metadata. Map these directly to:
file://<absolute-path-to-OUT_DIR>/<filename> as the URL--name from name--summary from description (fall back to name)--mime-type from mime_type--tags from subtype if present--extra from metadata as JSON if presentUse --root <dir> to target a scoped index (e.g. per-agent) instead of the default .asta/documents/.