skills.rest
apply-the
apply-theOFFICIAL
Explore all skills by this author →
GitHub

canon-inspect-artifacts

Return Canon-backed artifact paths under .canon/artifacts/<RUN_ID>/ for a run.

1|Updated Mar 26, 2026
Search Tags:#cli#artifacts#review#run#canon#inspect#artifact-paths
One-click install
npx skills add https://github.com/apply-the/canon --skill canon-inspect-artifacts
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: canon-inspect-artifacts
Source: https://github.com/apply-the/canon/tree/main/.agents/skills/canon-inspect-artifacts
Command: npx skills add https://github.com/apply-the/canon --skill canon-inspect-artifacts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Expose the emitted artifact paths from a Canon run to enable rapid review without inspecting run state or evidence lineage.

Core Features & Use Cases

  • Expose emitted artifact paths for a run to simplify validation and sharing.
  • Works with a provided RUN_ID or resolves the latest run, without requiring runtime state exploration.
  • Returns only Canon-backed artifact pointers under the .canon/artifacts/<RUN_ID>/ path to avoid leakage of unrelated data.

Quick Start

Provide a RUN_ID (or use the latest run) and run canon inspect artifacts to retrieve artifact paths.

Frequently Asked Questions about canon-inspect-artifacts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find artifact paths for a Canon run?▼

You can find Canon run artifact paths by providing a RUN_ID to the CLI, which validates Canon availability and returns exact artifact locations under .canon/artifacts/<RUN_ID>/.

What is the best way to review artifacts without inspecting run state or evidence lineage?▼

Reviewing Canon artifact paths directly bypasses run state and evidence lineage inspection, exposing only emitted artifact pointers for rapid validation and sharing without unrelated data leakage.

Do I need a RUN_ID to inspect Canon artifacts?▼

A RUN_ID is not strictly required to inspect Canon artifacts; the tool resolves the latest run automatically if no RUN_ID is provided, validating Canon availability before returning artifact paths.

Can I retrieve artifacts from paths outside the .canon/artifacts directory?▼

No, retrieving artifacts outside .canon/artifacts/<RUN_ID>/ is not supported. The tool strictly returns Canon-backed artifact pointers to prevent leakage of unrelated data during artifact path review.

Why does my Canon artifact inspection fail to return results?▼

Canon artifact inspection fails when Canon availability is missing or the specified RUN_ID does not exist. The tool explicitly validates both Canon availability and the run's existence before returning artifact paths.

Related Skills

Explore More Software Engineering Skills→
apply-theapply-the
1

canon-resume

Resume a Canon run from its recorded runtime state using RUN_ID.

Official
Advanced
apply-theapply-the
1

canon-requirements

Run bounded Canon requirements runs with RISK, ZONE, and authored inputs.

Official
Advanced
apply-theapply-the
1

canon-inspect-evidence

Retrieve evidence bundles, invocation lineage, and runtime surfaces for a Canon run.

Official
Intermediate
pabloimrik17pabloimrik17

openspec-ff-change

Automate creation of OpenSpec change artifacts within CLI workflows.

Community
Intermediate