Askr
Tooling

Agent Skills and Workflows

Use agent skills and workflows with the current published Askr packages.

  • @askrjs/askr0.0.59

How to use agent skills and workflows

Install the published project skills, keep them in version control, and review generated guidance against the current application before applying it.

  1. Import the published @askrjs/askr entrypoint.
  2. Keep agent skills and workflows configuration next to the component, route, or server composition root that owns it.
  3. Handle pending, unavailable, cancellation, and failure states, then verify the production path.
npx askr skills install
npx askr skills sync
npx askr skills review foundation --cwd .

git diff -- skills

Install skills

askr skills install [--cwd <dir>] [--force] copies the bundled Askr skills into a project's skills/ directory. It refuses to write into a non-empty skills/ directory unless you pass --force, which protects hand-authored or previously customized skills from being silently overwritten. New projects created with askr create already get this treatment automatically unless --no-skills was passed.

Sync skills

askr skills sync [--cwd <dir>] [--force] is the update path for an existing project: it overwrites the bundled askr-* skill folders with the current versions and removes any askr-* folders that are no longer part of the bundle, while leaving unrelated custom skill folders untouched. Run it after upgrading @askrjs/cli to pick up skill content changes without hand-diffing each file.

Review workflow

askr skills review <prompt-id> [--cwd <dir>] [--json] evaluates generated output against a deterministic rubric -- for example askr skills review foundation --cwd ./candidate-app checks a candidate project against the foundation prompt's rules, and askr skills review list shows the available prompt ids. Rubrics check concrete things like whether obsolete boolean or guest-string auth declarations show up in the code, or whether styling uses CSS var(--...) tokens and data-slot attributes instead of ad hoc classes.

Project ownership

Because sync only ever touches askr-* prefixed folders, any custom skill you add under a different name survives every sync indefinitely -- the bundled skills and your project-specific ones coexist in the same skills/ directory without stepping on each other. That naming convention is the entire mechanism; there's no separate manifest or config file tracking which folders are bundled versus custom.