another-skill

Enumerate skills in a repository by parsing SKILL.md frontmatter.

5|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/agentxm/axm --skill another-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: another-skill
Source: https://github.com/agentxm/axm/tree/main/packages/cli-e2e/src/fixtures/skills-repo/another-skill
Command: npx skills add https://github.com/agentxm/axm --skill another-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and enumerate all skills present in a repository, enabling automated validation of skill inventories.

Core Features & Use Cases

  • Discovery-driven testing: identifies all skills in a repository to validate the skill inventory for a project.
  • Multi-skill aggregation: groups discovered skills for batch testing and verification across agents.
  • Use Case: In a workspace with several skill definitions, automatically list all available skills for QA review.

Quick Start

Run the discovery workflow against the skills repository to enumerate all detected skills.

Frequently Asked Questions about another-skill

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

FAQPage Schema
How do I discover all skills in a repository for QA validation?

Skill discovery in a repository identifies and enumerates all available skills by parsing SKILL.md frontmatter to extract names and descriptions, validating the root directory for a valid entry point.

What is the best way to automate skill inventory auditing in a monorepo?

Automated skill inventory auditing scans multiple directories in a monorepo to group discovered skills for batch testing and verification across agents.

Can I use this discovery process for E2E testing of multiple skill collections?

Yes, skill discovery applies to monorepos or skill collections, enabling E2E testing by automatically listing all available skills for QA review.

Does skill discovery require parsing SKILL.md frontmatter to work?

Yes, the discovery process parses SKILL.md frontmatter to extract the skill name and description, and verifies the root directory contains a valid skill unit with an entry point.

How do I run a discovery workflow against a skills repository?

To run the discovery workflow, execute it against the skills repository to enumerate all detected skills, grouping them for batch testing and verification.

Are there limitations when discovering skills across multiple directories?

Discovery requires each skill to have a valid SKILL.md with frontmatter and a root directory containing a valid skill unit with an entry point; missing these will prevent proper enumeration.