AI Agent Hub
Back to skills
WorkBuddy Skill Map icon

WorkBuddy Skill Map

Data Analysis Updated 2026.08.30

Paste the following prompt into your AI chat to install this skill:

Please install @user_7ba94f9e/skill-map according to https://skillhub.cn/install/skillhub.md.

About this skill

Problem

When a machine has many WorkBuddy skills, their metadata is often scattered across SKILL.md, invocation logs, and project configuration. Engineers cannot quickly tell which skills belong to the same category, which can be chained by input → output, and which were once active but have recently become cold. skill.看一看 addresses this local skill visibility gap: it does not modify skills, but organizes existing data into an interactive map.html.

How It Works

It scans ~/.workbuddy/skills/ and .workbuddy/skills/, then reads frontmatter, local usage logs, and SkillHub hot data to generate a single-file offline HTML map. Key capabilities include:
- Inventory and taxonomy: a side list, force-directed graph, and 7-color category filtering help narrow focus.
- Workflow discovery: matches input and output declarations to show connectable chains, colored by activity state.
- Usage signals: node size reflects real invocation frequency, and a top section highlights recently cold skills.
- Fallback and export: supports offline fallback and --json export for secondary analysis.

Boundaries

It is a read-only visualization tool. It does not install, uninstall, enable, modify, route, or search for skills. map.html may expose the full list of local skill names, so redact it before sharing with untrusted people.

Use Cases

  • Audit locally installed skills and their category distribution across several dev machines.
  • Check whether one skill's declared input and output can feed the next workflow step.
  • Review local usage logs to find previously active skills that are recently cold.
  • Generate a single-file offline map and export structured data for downstream analysis.

Best For

  • Engineering leads maintaining WorkBuddy workspaces who need to audit local skill inventory and taxonomy.
  • Data engineers building workflows who need to check input-output compatibility between adjacent skills.
  • Technical ops staff taking over legacy projects who need to spot recently cold but previously active skills.
  • Platform engineers delivering offline reports who need a single-file map and structured data export.