Editorial Policy — Review Standards

SkillVetAI exists to help people make informed decisions about AI capabilities and concrete Agent Skill packages. This policy explains the evidence labels, editorial judgments, corrections, and commercial boundaries used during that work.

Content types

Capability guides

The /skills/ pages are editorial explanations of general workflows. They may include use cases, typical permissions, risk guidance, examples, alternatives, and troubleshooting. They are not installable package listings and do not establish that a particular repository or release behaves exactly as described.

Skill package records

The /packages/ records are published only when SkillVetAI can identify a canonical source and an immutable release using a registry version or commit SHA plus a content hash. Package pages distinguish publisher attribution, source claims, automatic inference, platform documentation, compatibility tests, external scan results, SkillVetAI scan results, and editorial conclusions.

Evidence statuses

Status Meaning Does not mean
Editorial overview Human-edited analysis of a capability A package was installed, scanned, or certified
Source verified Canonical source and fixed release confirmed The release is safe or works on every platform
Compatibility verified Fixed release reproduced on a recorded platform version Future releases or platform versions will work
Verification expired Previous evidence is outside its validity window The package is necessarily broken or malicious

No status means “guaranteed safe.” Automated scanners can produce false positives and false negatives.

Editorial assessments

Capability guides may show:

  • Editorial utility, 1–5: expected usefulness for the stated workflow;
  • Workflow complexity, 1–5: typical setup and operational effort;
  • Editorial risk, Low/Medium/High: potential impact of misuse or misconfiguration;
  • Typical permissions: access commonly required by implementations in the category.

These are explanatory judgments, not community ratings or measurements of a concrete package. Package-level maintenance will not be inferred from a generic capability guide.

Package-level evidence requirements

A package record should provide or clearly mark as unknown:

  • Publisher and canonical source;
  • Fixed release, Commit SHA, and content hash;
  • License evidence;
  • File inventory and dependencies;
  • Declared and inferred permissions;
  • Platform compatibility status and provenance;
  • Scan tool, version, policy, date, and findings;
  • Human review method and expiry date, when applicable.

Sources and citations

  • Prefer official documentation, canonical repositories, registries, standards, and primary research.
  • Link factual claims to the source where practical.
  • Label broad editorial research separately from package-level provenance.
  • Do not turn a third-party directory’s claim into a SkillVetAI fact without attribution.
  • Do not use deployment time as proof that source data was recently reviewed.

Safety and publication decisions

SkillVetAI does not publish or promote packages intended for malware, credential theft, phishing, unauthorized surveillance, security evasion, spam, or abuse. A package may be withheld or quarantined when evidence suggests malicious behavior, identity impersonation, hidden code loading, undeclared credential access, or another serious risk.

Reports, scans, and author responses are reviewed as evidence. Report volume alone does not prove wrongdoing. Affected publishers must have a reasonable correction or appeal channel except where immediate restriction is necessary to limit harm.

Corrections, removals, and version history

Submit errors, rights concerns, removal requests, or security reports through the Contact page. Material corrections should preserve a record of what changed and when. Removed or deprecated package history may remain as a factual security or compatibility record when legally permitted and useful to existing users.

Freshness

Dates have different meanings and must not be collapsed into one generic update label:

  • Source updated;
  • Last indexed;
  • Last scanned;
  • Last compatibility tested;
  • Last editorial review.

Evidence can expire. Popularity does not extend a verification period.

Sponsorship and commercial independence

  • Sponsored placement is clearly labelled.
  • Payment cannot purchase a better risk result, Verified status, or natural ranking.
  • Paid review can purchase service scope and response time, not approval.
  • Affiliate relationships, if any, are disclosed near the relevant link.
  • Material conflicts of interest must be stated on the affected page.

Current transition

SkillVetAI now publishes both source- and version-backed package records and editorial capability guides. A /packages/ page must identify a concrete source and fixed release. A /skills/ page remains an editorial capability guide unless it explicitly links to a separate package record. The About page explains this distinction in plain language.