Agent Capability Discovery
- 204 installs
- 2 repo stars
- Updated January 25, 2026
- jorgealves/agent_skills
Map what an agent can already do—tools, skills, APIs, and gaps—before scoping new work so teams avoid duplicate tooling and missed integration opportunities.
About
agent-capability-discovery from jorgealves/agent_skills helps teams audit an agent's current toolbox and integration surface, producing a clear map of strengths, gaps, and next capabilities to add before prototyping or coding.
- Inventory existing agent tools and skills
- Identify missing capabilities versus requirements
- Compare planned workflows to available actions
- Document integration and permission gaps
- Prioritize capability backlog before build
Agent Capability Discovery by the numbers
- 204 all-time installs (skills.sh)
- +9 installs in the week ending Aug 2, 2026 (Skillselion tracking)
- Ranked #2,833 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 2, 2026 (Skillselion catalog sync)
npx skills add https://github.com/jorgealves/agent_skills --skill agent-capability-discoveryAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 204 |
|---|---|
| repo stars | ★ 2 |
| Last updated | January 25, 2026 |
| Repository | jorgealves/agent_skills ↗ |
What it does
Map what an agent can already do—tools, skills, APIs, and gaps—before scoping new work so teams avoid duplicate tooling and missed integration opportunities.
Files
Agent Capability Discovery
Purpose and Intent
The agent-capability-discovery skill is the "brain" of a multi-agent system. It allows an agent to self-reflect and understand what tools and expertises are available within its environment by indexing all skill.yaml files.
When to Use
- System Initialization: Run this when an agent starts up to populate its internal tool list.
- Routing Decisions: Use this when a master agent receives a complex user request and needs to identify which specialized skill (e.g.,
hipaa-compliance-guardvs.pii-sanitizer) is best suited for the job. - Documentation Generation: Automatically keep a "Global Skills Map" up to date for human developers.
When NOT to Use
- Skill Execution: This skill only discovers what is possible; it does not execute the other skills.
- External Tooling: It only indexes skills defined in the local repository structure.
Input and Output Examples
Input
base_directory: "."
output_format: "markdown"Output
A markdown table or JSON object listing all discovered skills, their descriptions, and their primary capabilities.
Error Conditions and Edge Cases
- Broken YAML: If a
skill.yamlis malformed, the discovery tool will skip that directory and report a warning. - Circular Dependencies: This tool does not handle execution dependencies, only discovery.
Security and Data-Handling Considerations
- Metadata Only: The tool only reads the definition files; it never touches actual source code or data unless instructed by the indexed skills themselves.
- Local Scope: Discovery is confined to the provided root directory to prevent directory traversal attacks.
name: agent-capability-discovery
version: 1.0.0
description: Scans all skill directories in the repository to generate a comprehensive global map of agent capabilities, inputs, and outputs. Use when you need to understand the full potential of your agent library or when a master agent needs to decide which sub-agent skill to invoke for a complex task.
inputs:
base_directory:
type: string
description: The root directory containing all agent skill folders.
default: "."
output_format:
type: string
enum: [json, markdown, yaml]
default: markdown
outputs:
capabilities_map:
type: string
description: A structured mapping of all discovered skills and their primary functions.
capabilities:
- Recursive directory traversal to identify skill folders.
- Extraction of 'capabilities' and 'description' from skill.yaml.
- Categorization of skills based on their name or metadata.
- Generation of a routing table for agentic decision-making.
constraints:
- Only scans directories containing a valid skill.yaml file.
- Accuracy depends on the clarity of descriptions in the target skills.
security:
- Reads metadata only; no execution of third-party code.
- Operates strictly within the provided base_directory.
examples:
- input:
base_directory: "./agent-skills"
output_format: "markdown"
output:
capabilities_map: "| Skill | Capability |\n| --- | --- |\n| secret-leak-detector | Scans code for secrets |"Related skills
Setup Matt Pocock SkillsScaffold the per-repo configuration that Matt Pocock’s engineering agent skills rely on so they understand the issue tracker, triage labels, and domain documentation la495k196k
Lark AppsConnect Claude, Cursor or custom agents directly to Lark (Feishu) for messaging, document automation, approval workflows and enterprise data access.402k
CavemanSlash token usage by roughly 75% while keeping every technical detail intact when working with Claude Code, Cursor or similar agents.391k94.7k
Lark Skill MakerQuickly turn any Lark/Feishu OpenAPI call or multi-step workflow into a reusable agent skill with its own SKILL.md.386k16k
Running Claude Code Via Litellm CopilotRun Claude Code at a fraction of the cost by routing requests through LiteLLM to the GitHub Copilot Chat API.270k72
Codex PetGenerate a complete Codex Pet spritesheet and metadata from one reference image without needing an OpenAI key or Codex Pro.246k10