check-skill

Validate oxo-call skill.md files against local and online documentation.

1|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/Traitome/oxo-call-extends --skill check-skill-traitome
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-skill
Source: https://github.com/Traitome/oxo-call-extends/tree/main/check-skill
Command: npx skills add https://github.com/Traitome/oxo-call-extends --skill check-skill-traitome

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill checks and updates an oxo-call skill.md by validating local tool usage, collecting command help outputs, and cross-referencing online documentation to ensure accuracy and completeness.

Core Features & Use Cases

  • Cross-verifies local tool availability via PATH, package managers, and container environments.
  • Aggregates help outputs and online references to fill in missing concepts, pitfalls, and examples.
  • Produces an updated, production-ready skill.md that remains consistent with real-world tool usage and documentation.

Quick Start

Update a target skill.md by running the skill check to audit and merge improvements into the file.

Frequently Asked Questions about check-skill

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

FAQPage Schema
How do I validate a skill.md file for accuracy against local tools and online documentation?

Validating a skill.md involves parsing local environments for tool availability via PATH and package managers, collecting --help outputs, and cross-referencing online documentation to merge corrections into a production-ready file.

What's the best way to find gaps and inconsistencies in skill documentation?

Finding gaps in skill documentation requires cross-verifying local tool availability, aggregating CLI help outputs, and checking online references to identify missing concepts, pitfalls, and examples across multiple sources.

Does skill validation work with tools installed in container environments?

Skill validation works with container environments by checking local tool availability across PATH, package managers, and container configurations, ensuring the documentation accurately reflects real-world usage.

How do I update skill documentation with correct usage examples and pitfalls?

Updating skill documentation happens by retrieving remote docs, parsing local tool help outputs, and merging these findings to append accurate concepts, pitfalls, and examples into a corrected skill file.

When should I run a skill check on my bioinformatics automation documentation?

Running a skill check is necessary when a skill.md needs quality-control validation to ensure broad real-world coverage, verifying that documented tool usage matches actual local and remote reference behavior.

Why does my skill documentation show incorrect tool usage and missing pitfalls?

Incorrect tool usage and missing pitfalls occur when skill documentation is not cross-referenced with local help outputs and online references, leading to inconsistencies between written examples and real-world tool behavior.