Artifact validation

Skill IrfanSadiqRahat/constellation/methodology/artifact-validation

Mechanical schema + invariant checking of artifacts. The unit test for typed handoffs.From its SKILL.md

Install

npx -y skills add IrfanSadiqRahat/constellation --skill artifact-validation

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.1 KB, 470 tokens by cl100k_base, as published. Nobody here has run it

artifact-validation

When activated

An artifact has been produced and is about to be handed off. Before handoff-protocol ships it, artifact-validation proves it conforms.

Checks performed

artifact_id: <id>
artifact_type: <type>
checks:
  - id: schema_present
    passed: bool
  - id: schema_valid
    passed: bool
    errors: [<jsonpath + reason>]
  - id: required_fields_filled
    passed: bool
    missing: [<field>]
  - id: enum_constraints
    passed: bool
    violations: [<field>]
  - id: invariants
    items:
      - rule: <e.g. "every requirement has acceptance criteria">
        passed: bool
        offenders: [<id>]
  - id: link_integrity
    passed: bool
    broken_links: [<url>]
  - id: artifact_freshness
    passed: bool
    age: <duration>
overall: pass | fail

Invariant library (extensible)

artifact type	invariants
PRD	every must-have requirement has acceptance criteria; KPI set; non-goals declared
BackendArchitecture	every service has owner; persistence chosen; SLOs declared
ThreatModel	every component has STRIDE coverage; mitigations have owners
ApiContract	every operation has 4xx/5xx response; error envelope declared; auth scheme
EvalSuite	metrics have targets; datasets are versioned; gates declared
DataArchitecture	every dataset has owner; PII tagged; retention set
MigrationPlan	expand/contract phases present; rollback declared; rate limit set
PostmortemDoc	timeline present; action items have owners + dates; blameless

Implementation

artifact-validation is mechanical — runs as a tool. Each artifact type has a validator under tools/validators/<type>.mjs. Adding a type means adding a validator and the artifact catalog gets richer.

Why this matters

This is an automated gate, like a type-checker for thinking outputs. The difference between "we agree it looks done" and "the schema checker says it's done".

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.