Validate artifact

Skill frankxai/marine-agent-skills/skills/validate-artifact

Use to run the Blue Life Commons schema validator over a draft artifact's frontmatter before opening a PR. Triggers — "validate this artifact", "does this pass the schema", before /open-artifact-pr.From its SKILL.md

Install

npx -y skills add frankxai/marine-agent-skills --skill validate-artifact

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

One thing to look at

0 stars0 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

1.3 KB, 264 tokens by cl100k_base, as published. Nobody here has run it

Validate artifact (schema gate)

The commons ships a deterministic schema validator. Run it; do not eyeball.

Procedure

Ensure the draft has complete YAML frontmatter (required: id, type, title, status, sources, review, outputs, contributors, license).
From the repo root, run the project's validator:
```
python scripts/validate_artifacts.py content/path/to/your-artifact.md
```
(No args scans all of content/ and missions/.)
If marine-mcp is available, you can also self-check frontmatter via its validate_artifact tool before touching the filesystem.

Interpreting results

OK <file> — passes the schema.
FAIL <file> followed by - <field>: <message> — fix each before PR. Common causes: missing review block, empty sources, id not matching ^[a-z0-9]+(-[a-z0-9]+)*$, species_group value outside the enum.

The CI workflow validate-artifacts.yml runs this on every PR — a local failure is a guaranteed CI failure. Fix locally first.

Built on SIP · Blue Life Commons.

What ships with it

Read from the repository

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