external-skill-review

Assess external skill candidates against repository policy and catalog provenance.

1|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/t-uda/skills --skill external-skill-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: external-skill-review
Source: https://github.com/t-uda/skills/tree/main/skills/external-skill-review
Command: npx skills add https://github.com/t-uda/skills --skill external-skill-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill helps teams review candidate external skills against the repo policy, preventing adoption of unvetted capabilities and ensuring governance.

Core Features & Use Cases

  • Validate inputs (repo, skill_path, pinned_ref) and required metadata against policy.
  • Check the local catalog .agents/approved-external-skills.json to determine approval status or if manual review is needed.
  • Produce a catalog-ready provenance entry and guidance for installation steps once approved.

Quick Start

Provide the upstream repo, skill_path, and pinned_ref to start a catalog review.

Frequently Asked Questions about external-skill-review

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

FAQPage Schema
How do I audit external skills against repository policy?

You can audit external skills by supplying the upstream repo, skill_path, and pinned_ref. The review workflow validates required metadata, licensing, risk content, and provenance, returning a structured status with actionable guidance for cataloging.

What is external skill provenance and when do I need to review it?

External skill provenance is the recorded origin and approval status of a candidate capability. You need to review it before adoption to prevent unvetted capabilities and ensure governance compliance across your repository.

How do I check if an external skill is approved in the local catalog?

To check if an external skill is approved, the review process queries the local catalog file `.agents/approved-external-skills.json`. It determines whether the skill has existing approval status or requires manual review against policy.

What inputs do I need to validate an external skill candidate?

You need to provide the upstream repo, skill_path, and pinned_ref to validate an external skill candidate. These inputs are checked against repository policy alongside required metadata to ensure governance before adoption.

What does the external skill review workflow return after validation?

The external skill review workflow returns a structured result containing a status and actionable guidance. It also produces a catalog-ready provenance entry detailing installation steps once the skill is approved.