Browse and pick (recommended)
npx skills add https://agent-skills.bespoketech.com.ngDocumentation
Install, inspect, and contribute.
BAS uses the open Skills CLI. No BAS wrapper, account, or production database is required. The catalogue currently publishes 9 skills.
Before you start
- Node.js 20 or newer, so that npx can fetch the CLI.
- Network access to this domain, or to github.com if you install from the repository.
- A writable project directory for project scope, or user-level agent directories for global scope.
From this domain
Resolves the published discovery index and installs verified archives. Use this unless you need an unreleased change.
List everything available
npx skills add https://agent-skills.bespoketech.com.ng --listInstall one skill into this project
npx skills add https://agent-skills.bespoketech.com.ng --agent '*' --skill bespoke-quality-workflow --yesInstall one skill globally
npx skills add https://agent-skills.bespoketech.com.ng --global --agent '*' --skill bespoke-evidence-gate --yesInstall the whole catalogue
npx skills add https://agent-skills.bespoketech.com.ng --skill '*' --agent '*' --yesFrom the GitHub repository
Clones the repository and reads the packages under skills/. Use this to install a change that has not been published yet.
List skills in the repository
npx skills add https://github.com/Bespoke-Technologies/agent-skills --listInstall one skill from the repository
npx skills add https://github.com/Bespoke-Technologies/agent-skills --agent '*' --skill bespoke-quality-workflow --yesWithout installing
Prints the skill instructions for a single request. Nothing is written to disk.
Load instructions for one request
npx skills use https://agent-skills.bespoketech.com.ng --skill bespoke-quality-workflowTroubleshooting
Installation problems almost always surface as two stacked messages. The second one is the fallback, not the cause.
No well-known skills found; trying direct download…
Why it happens. The CLI could not parse a discovery index at /.well-known/agent-skills/index.json or /.well-known/skills/index.json, so it fell back to downloading the URL directly.
What to do. Confirm the index resolves and declares the v0.2.0 discovery schema. If you are pointing at your own host, publish the schema field — an index without it is read as the legacy format and rejected when entries omit description and files.
Downloaded URL is not a valid SKILL.md file or supported archive
Why it happens. This is the fallback failing, not the real error. The CLI downloaded the page at the URL, received the HTML site, and could not read it as a skill.
What to do. Treat the discovery step above as the actual fault. Re-run with the index URL directly to see whether it parses.
A skill is listed but silently never installs
Why it happens. The CLI recomputes the sha256 digest of each downloaded archive and discards the skill when it does not match the digest in the index.
What to do. Re-run the command; if it persists the published index is stale against its artefacts and needs regenerating.
The whole catalogue installs when you wanted one skill
Why it happens. A per-skill URL still resolves the full index. Selection is done with a flag, not with the URL path.
What to do. Pass --skill <name> to choose one skill, or --skill '*' to take all of them.
Failed to install: Eve / PromptScript does not support global skill installation
Why it happens. Not a failure of the skill or this catalogue. Eve and PromptScript are the only 2 of the CLI's 57 known agents with no user-level skills directory — they are project-scoped by design — so combining --global with them is a request that cannot be satisfied. The skill still installed everywhere else; check the 'Installed' summary above the error.
What to do. Ignore it, or avoid targeting them: pass --agent with the agents you actually use instead of --agent '*'. Installing at project scope instead of --global also avoids it entirely.
An --agent style flag seems to be ignored
Why it happens. The only agent flag is --agent (-a). An unrecognised flag such as --claude is silently discarded, and the CLI then falls back to installing into every detected agent.
What to do. Use --agent <name>, for example --agent claude-code, or --agent '*' when you genuinely want all of them.
To inspect discovery yourself, open /.well-known/agent-skills/index.json. It must return JSON whose $schema is the v0.2.0 discovery schema.
curl -sS https://agent-skills.bespoketech.com.ng/.well-known/agent-skills/index.jsonCompatibility
BAS packages follow the portable Agent Skills format and are published through the standard well-known discovery endpoints, so any conforming client can resolve them. The public builder exercises the current open Skills CLI with all-agent and Codex targets; no wider provider execution claim is made.
Frequently asked questions
Do I need an account, API key, or database?
No. The catalogue is static files served over HTTPS, and the CLI is the open-source skills package. Nothing here authenticates you.
Which agents can run these skills?
Any client that reads the portable Agent Skills package format. The CLI writes into the agent directories it detects on your machine; --agent '*' targets all of them.
What is the difference between project and global installation?
Project installation writes into the current repository, so the skill travels with the codebase. Global installation writes to user-level agent directories and applies everywhere.
How do I verify a skill before running it?
Every catalogue entry links its full SKILL.md source, declared permissions, network access, security-review status, and stated limitations. Skills run with full agent permissions, so read the source first.
How are updates released?
Each package is versioned and its archive is immutable once published: a changed package must ship under a new version rather than replacing an existing one.
Contributing
Add a complete portable skill under skills/, generate its provider metadata, declare its public catalogue metadata, and run every repository validator. A valid skill appears on the site without editing a website component.
Read the full contribution rules, or go straight to the repository contribution guide.