Skip to content

Missing /als:deploy skill — no skill bridges 'module authored' to 'skills invokable' #2

@klueless-io

Description

@klueless-io

Summary

Confusing operator flow — the path from 'I authored a module' to 'I can invoke its skills' is unclear. The deploy step (/als:deploy or equivalent) is missing from the skill set entirely.

Category

Bug report / UX gap

Conversation Context

This issue surfaced during a real authoring session on a project called FliLaunch. The operator had manually scaffolded a module (fli-launch, 1 Delamain, 2 skills) and the compiler was passing (alsc validate — 1 module, 0 errors).

Human: how do we run the delamain

AI: Described a 4-step flow: (1) alsc deploy claude, (2) bun install in dispatcher/, (3) create a session record, (4) bun run src/index.ts. Framed the deploy as a manual CLI step.

Human: no that is not how you run a delamain, surely its a skill

AI: Invoked /als:foundry — wrong skill (that's for importing pre-built modules). Then identified the two scaffolded skills (fli-launch-manage, fli-launch-pipeline) and explained they needed alsc deploy claude first to land in .claude/skills/.

Human: alsc deploy is not a skill, should there be a skill to do that for us?

AI: Checked als:reboot (restarts downed dispatchers — no deploy), als:install (deploys but only during first-time bootstrap), als:bootup (starts dispatchers, explicitly assumes .claude/delamains/ already exists). Confirmed: no skill covers the deploy step on an existing system after module authoring or changes.

The Gap

als:bootup is the power button but it assumes deployment has already happened. als:install is first-touch only. After any module authoring or changes to .als/, the operator must manually run:

bun /path/to/alsc/compiler/src/cli.ts deploy claude .

This command is not surfaced anywhere in the skill set. An operator following the natural flow (author → run) has no skill to bridge the gap.

Expected Behaviour

There should be an /als:deploy skill (or equivalent) that runs alsc deploy claude on the current system. Ideally als:bootup either calls it automatically, or the operator is prompted to deploy first if .claude/delamains/ is missing or stale.

Environment

  • ALS: 0.1.0-beta.28
  • Platform: Darwin arm64
  • Shell: /bin/zsh

Filed via /ghost-line

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions