dsh-praxis

Usage

No manual configuration is needed after installation: when the model encounters a trigger scenario from the skill catalog during a session, it loads the matching skill automatically. You can also specify directly in conversation, for example:

First give me an implementation plan (implementation-blueprint), then execute it (blueprint-execution).

When troubleshooting, the model prioritizes the fault-isolation workflow; before claiming completion, it provides verification evidence per completion-proof. Skills explicitly mark dependencies between each other via **REQUIRED SUB-SKILL:** praxis:xxx.

Plugin configuration

The plugin line supports two optional config fields (written in the profile's cordis.patch.yml or a --patch overlay):

- insert:
    - id: praxis
      name: dsh-praxis
      config:
        providerName: praxis-bundled   # provider name registered on ctx.skills (default)
        skillsDir: ./skills            # skill root directory; relative paths resolve against package root; array accepted

• providerName: a non-empty string; must be unique within the same scope (duplicate registrations are rejected by the registry).
• skillsDir: one or more skill root directories. Default is /skills (registered with bundled source at rank 600; explicitly configured directories register with custom source at rank 300, consistent with the platform's custom-directory semantics). Two standard layouts are accepted within a directory: /SKILL.md directory bundles, or flat .md files; the frontmatter name must match the directory/file name, otherwise the entry is skipped with a warning.