/ 
Developer-Dashboard-2.37
/ skills

NAME

skills - private built-in command wrapper for Developer Dashboard

SYNOPSIS

dashboard skills ...

DESCRIPTION

This private helper is staged under ~/.developer-dashboard/cli/dd/ so the public dashboard entrypoint can stay a thin switchboard.

PURPOSE

This staged helper exposes dashboard skills, the command family that installs, updates, lists, enables, disables, and uninstalls skills while also serving as the private handoff target for dotted skill command execution.

WHY IT EXISTS

It exists because skill lifecycle management is a built-in feature, but the wrapper should stage a command and leave Git/layout logic to the skill manager and skill command dispatch to the dedicated runtime module.

WHEN TO USE

Use this file when changing the dashboard skills CLI verbs or the dotted-command handoff into the skill runtime.

HOW TO USE

Users run dashboard skills install, update, enable, disable, list, usage, or uninstall. The staged helper forwards those lifecycle requests into the private runtime, which loads the skill manager and performs the requested action. The public dotted form dashboard <repo-name>.<command> also lands here through an internal action so installed skill commands keep one private helper surface.

WHAT USES IT

It is used by developers managing installed skills, by dotted skill command dispatch, by skill lifecycle tests, and by documentation that explains the isolated skill runtime.

EXAMPLES

Example 1:

dashboard skills install git@github.com:user/example-skill.git

Install one Git-backed skill into its isolated runtime root.

Example 2:

dashboard skills list

Inspect installed skill metadata, including whether each skill ships config, docker roots, aptfile, or cpanfile.

Example 3:

dashboard example-skill.hello

Run an installed skill command through the public dotted route, which the switchboard forwards into this staged helper.

Example 4:

~/.developer-dashboard/cli/dd/skills --help

Inspect the staged helper directly after dashboard init or helper extraction has populated the home runtime.

Example 5:

prove -lv t/05-cli-smoke.t t/19-skill-system.t

Rerun the focused staged-helper and thin-loader tests after changing helper dispatch behavior.

Example 6:

prove -lr t

Verify that the helper still behaves correctly inside the complete repository suite.