skill-system-graph

Build a canonical dependency graph from SKILL.spec.yaml files.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/arthur0824hao/ExperimentPipeline --skill skill-system-graph
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-system-graph
Source: https://github.com/arthur0824hao/ExperimentPipeline/tree/main/.agents/skills/skill-system-graph
Command: npx skills add https://github.com/arthur0824hao/ExperimentPipeline --skill skill-system-graph

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires psycopg2, PyYAML, and includes scripts (resource) components.

What problem does it solve?

Graph navigation and dependency analysis for skills by turning scattered SKILL.spec.yaml files into a canonical, PostgreSQL-backed behavior graph that can be queried for dependencies and delegation relationships.

Core Features & Use Cases

  • AI-first navigation of the skill graph, normalizing depends_on and delegates_to into a queryable model stored in PostgreSQL.
  • CLI primitives for topology inspection: show reads from the current spec-scan model; neighbors, path, and impact query persisted edges.
  • Incremental refresh using source hashes to keep the graph up to date without full rebuilds.

Quick Start

Run the graph CLI to display and navigate the current skill dependency graph.

Frequently Asked Questions about skill-system-graph

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

FAQPage Schema
How do I build a dependency graph from SKILL.spec.yaml files?

To build a dependency graph from SKILL.spec.yaml files, this Skill parses v1 and v2 specifications to normalize depends_on and delegates_to relationships, storing the canonical edges in a PostgreSQL database for querying.

How do I navigate skill dependencies using a PostgreSQL-backed graph?

You can navigate skill dependencies by running CLI primitives like show, neighbors, path, and impact, which query the persisted PostgreSQL graph to return JSON-first output for automation.

Does this dependency graph CLI require a full rebuild when specs change?

No, a full rebuild is not required. The CLI refresh operation uses source hashes to perform incremental updates, keeping the PostgreSQL-backed graph up to date efficiently after SKILL.spec.yaml changes.

Do I need PostgreSQL to analyze skill dependencies with this CLI?

You need SKILL.spec.yaml files for parsing, a PostgreSQL database for storing graph edges, and the psycopg2 and PyYAML dependencies installed to execute sync-graph and navigation operations.

What is the best way to inspect the impact of changing a skill dependency?

The best way to inspect impact is using the CLI impact primitive, which queries the persisted PostgreSQL graph to identify downstream dependent skills, returning JSON-first output suitable for automation.

Can I parse both v1 and v2 skill specifications into the dependency graph?

Yes, the graph parser normalizes both v1 and v2 skill specifications, extracting depends_on and delegates_to relationships to build a canonical, queryable behavior graph in PostgreSQL.