skill-trust-policy

Skill Trust Policy

Documentation examples may contain captured seeded counts, scores, timestamps, or health values. They are examples, not live telemetry. Use the running CLI status command or MCP index_status for current instance data.

Skill Trust and Review Policy

Zagros does not treat a contributed skill as trusted merely because it is installable.

Trust states

maintained — reviewed and maintained by the Zagros project.
community-reviewed — third-party contribution that passed contract, provenance, security, and evaluation review.
experimental — useful but not yet covered by a stable compatibility promise.
rejected/quarantined — fails provenance, safety, licensing, or behavior requirements.

Review requirements

A contributed skill must pass:

Provenance and license review — authorship and third-party material are identified; redistribution terms are compatible.
Security review — no credential harvesting, hidden network destinations, unsafe shell instructions, or unapproved writes.
Contract validation — required metadata/files and contract version are valid.
Behavior review — evals demonstrate intended behavior and important refusal/approval boundaries.
Integration review — declared MCP/tool dependencies match the actual references and compatibility metadata.

New remote MCP endpoints are security-sensitive and require explicit review of authentication, data handling, write capabilities, and returned-content trust boundaries.

Publication

Community skills are not promoted to maintained status automatically. Trust status must be explicit in skill-meta.yml. Material behavior or dependency changes require renewed review.