@qentrah/skills

Documentation · Install guide

Install canonical Qentrah agent skills from their public GitHub repositories.

These guides describe the published 0.2.0 package. The examples use the APIs and files in that release; beta packages should be kept on matching versions.

Documentation

• Install and verify
• Choose a skill
• Install skills in automation
• API and exports
• Troubleshooting

Install and verify

Before you start

• node: >=20.

Use a project with a package.json. Check the runtime and package manager:

node --version
npm --version

Install the documented version

npm install @qentrah/[email protected]

Confirm the installation

npm ls @qentrah/skills

The output should show @qentrah/[email protected]. Commit the lockfile so another developer installs the same dependency tree.

Usage

npx @qentrah/skills
npx @qentrah/skills list
npx @qentrah/skills add architecture-guardian
npx @qentrah/skills add code-review ui-implementation

Running the CLI without a skill name opens an interactive multi-select. Use the arrow keys to navigate, Space to select multiple skills, and Enter to continue.

By default, a skill is installed in .agents/skills/<skill-name> in the current project. Use --cwd <directory> to choose another project or --force to replace an existing installation.

For non-interactive automation:

npx @qentrah/skills add --all --yes

Expected result

An installed skill has a SKILL.md inside .agents/skills/<skill-name> under the selected project. Read it before enabling the skill in an agent.

Choose a skill

Available skills

| Skill | Install | Source | | --- | --- | --- | | Architecture Guardian | npx @qentrah/skills add architecture-guardian | qentrah/skill-architecture-guardian | | Code Review | npx @qentrah/skills add code-review | qentrah/skill-code-review | | Content Design | npx @qentrah/skills add content-design | qentrah/skill-content-design | | Design Critique | npx @qentrah/skills add design-critique | qentrah/skill-design-critique | | Release Readiness | npx @qentrah/skills add release-readiness | qentrah/skill-release-readiness | | Repository Guide | npx @qentrah/skills add repository-guide | qentrah/skill-repository-guide | | UI Implementation | npx @qentrah/skills add ui-implementation | qentrah/skill-ui-implementation |

Every skill has its own public GitHub repository under Qentrah, where its SKILL.md and documentation can be reviewed or edited.

Install skills in automation

Select the project explicitly

Use Node.js 20 or later and a network connection to the public GitHub skill repositories.

npx @qentrah/[email protected] list
npx @qentrah/[email protected] add code-review ui-implementation --cwd ./my-app --yes

Install all canonical skills

npx @qentrah/[email protected] add --all --yes --cwd ./my-app

The destination is .agents/skills under the selected project. Keep the installed SKILL.md files reviewable in source control if your project shares agent instructions.

Replacing an installation

Add --force only when you intend to replace existing installed files. Review local edits first. A skill name identifies its canonical source repository; the package is an installer, not an agent runtime or permission manager.

API and exports

Package identity

| Field | Value | | --- | --- | | Package | @qentrah/skills | | Version inspected | 0.2.0 | | License | MIT | | Module type | commonjs |

Public import paths

The manifest uses main = index.js. Read the bundled declaration files when available.

CLI entry points

• qentrah-skills → bin/qentrah-skills.mjs.

Inspect the original release

Open the versioned npm page or download its published archive. The archive includes the actual executable files and declarations used to write these guides.

Troubleshooting

Check the installed version

npm ls @qentrah/skills

Compare the installed version with the version noted in this guide. Inspect your lockfile before changing dependencies; prerelease behavior may differ between versions.

Import or module errors

Use only public import paths listed in API and exports. Avoid importing guessed paths inside dist. ESM-only packages require an ESM-aware application. Install declared peer dependencies in the consuming application.

Existing skill directory

Without --force, preserve the existing installation and choose another destination if needed. --force replaces an existing installation. Run list first to check the canonical name; use --cwd to select the intended project rather than relying on the terminal’s current directory. Network or GitHub access failures can prevent fetching a skill; keep the existing files until the installation succeeds.

Release documentation

Documentation checked against the previously published package artifact. This documentation-only release preserves executable files and dependencies.