What a skill does
It gives the agent a professional framework, requires evidence and explicit assumptions, checks risk, and produces a useful working artefact.
Installation guide and reference
Two portable Agent Skills packages for business analysts, product owners and teams building products with Claude Code or Codex.
A skill is a folder centred on a SKILL.md file. It describes when to use the skill, the workflow, checks and expected output. Supporting references are loaded only when needed. It is not a separate application, model or data store.
It gives the agent a professional framework, requires evidence and explicit assumptions, checks risk, and produces a useful working artefact.
It does not replace product ownership, legal advice or security expertise; guarantee unreviewed code; or grant the agent additional permissions.
The core delivery toolkit, from framing the product through to a controlled release. Designed for day-to-day MVP development and the evolution of a live product.
Download Core Deliveryba-po-core-delivery.zip
The production-readiness layer: security, data protection, observability, recovery, public demos, UX and incident coordination.
Download Production Governanceba-po-production-governance.zip
Extract the ZIP files, then copy the contents of each skills folder into the personal skills directory used by your tool. The commands below install both packages.
skills folder inside.⌘ Shift . to show hidden folders. In Windows File Explorer enable View → Hidden items..agents/skills for Codex or .claude/skills for Claude Code.framing-digital-products, into that directory. Do not copy the outer package folder.This option is for users comfortable with Terminal or PowerShell. Replace /path/to or C:\path\to with the actual location of the extracted folders.
After extraction, you should have the folders ba-po-core-delivery and ba-po-production-governance.
macOS / Linux — replace the paths with your extracted folders:
mkdir -p "$HOME/.agents/skills"
cp -R "/path/to/ba-po-core-delivery/skills/." "$HOME/.agents/skills/"
cp -R "/path/to/ba-po-production-governance/skills/." "$HOME/.agents/skills/"Windows PowerShell:
New-Item -ItemType Directory -Force "$HOME\.agents\skills"
Copy-Item -Recurse -Force "C:\path\to\ba-po-core-delivery\skills\*" "$HOME\.agents\skills\"
Copy-Item -Recurse -Force "C:\path\to\ba-po-production-governance\skills\*" "$HOME\.agents\skills\"find "$HOME/.agents/skills" -maxdepth 2 -name SKILL.mdRestart Codex if the skills do not appear automatically. In an interactive session, open /skills or invoke a skill as $framing-digital-products.
Claude Code needs the folders inside skills; the Codex plugin manifest does not need to be copied.
macOS / Linux — replace the paths with your extracted folders:
mkdir -p "$HOME/.claude/skills"
cp -R "/path/to/ba-po-core-delivery/skills/." "$HOME/.claude/skills/"
cp -R "/path/to/ba-po-production-governance/skills/." "$HOME/.claude/skills/"Windows PowerShell:
New-Item -ItemType Directory -Force "$HOME\.claude\skills"
Copy-Item -Recurse -Force "C:\path\to\ba-po-core-delivery\skills\*" "$HOME\.claude\skills\"
Copy-Item -Recurse -Force "C:\path\to\ba-po-production-governance\skills\*" "$HOME\.claude\skills\"find "$HOME/.claude/skills" -maxdepth 2 -name SKILL.mdStart Claude Code and ask “What skills are available?”, or invoke one directly: /framing-digital-products. If ~/.claude/skills was first created during the current session, restart Claude Code.
| Tool | Directory at project root | When to choose it |
|---|---|---|
| Codex | .agents/skills/ | When the set should be version-controlled and limited to this team or repository. |
| Claude Code | .claude/skills/ | When the skills are product-specific and should travel with the repository. |
~/.claude/skills folder on your computer. The two package archives above are intended for Codex and Claude Code. For Claude.ai, download the individual ZIP for the skill you need from the catalogue below and upload it through Customize → Skills. A cloud session may also use project skills committed to the repository where the selected mode supports them.
Describe the task naturally. The agent matches it to installed skill descriptions and loads the relevant one. For example: “Turn these rating rules into a decision table and boundary tests.”
Name the skill directly: $skill-name in Codex or /skill-name in Claude Code. Follow it with the task and links to relevant files.
# Codex
$designing-ai-features Review the proposed CV analysis flow. Define the schema,
validation, human review and no-AI fallback.
# Claude Code
/reviewing-ai-generated-code Review the current diff against the acceptance
criteria. Do not edit files; report evidence and risks first.Each skill is designed to finish with a structured output—a table, map, checklist, verification plan or decision log—rather than generic advice.
framing-digital-productsDownload skill (.zip)Claude.ai · Claude Code · CodexClarifies users, outcomes, MVP boundaries, data, roles, risks, assumptions and measurable acceptance criteria before implementation starts.
designing-access-modelsDownload skill (.zip)Claude.ai · Claude Code · CodexConnects roles, data ownership, actions and restrictions, exposing mismatches between the UI, API and row-level policies.
modelling-business-rulesDownload skill (.zip)Claude.ai · Claude Code · CodexTurns formulas, statuses, eligibility and transitions into unambiguous decision tables, invariants and boundary examples.
designing-ai-featuresDownload skill (.zip)Claude.ai · Claude Code · CodexDesigns an AI feature as a controlled pipeline: minimum data, a clear model role, structured output, validation, human review and fallback.
evaluating-ai-qualityDownload skill (.zip)Claude.ai · Claude Code · CodexCompares models, prompts and schemas on a representative evaluation set, covering quality, cost, latency and critical failures.
directing-coding-agentsDownload skill (.zip)Claude.ai · Claude Code · CodexTurns a change or defect into a bounded, evidence-driven task for Codex, Claude Code or another coding agent.
reviewing-ai-generated-codeDownload skill (.zip)Claude.ai · Claude Code · CodexReviews a diff against product intent, business rules, access control, data safety, tests and agreed scope.
releasing-digital-productsDownload skill (.zip)Claude.ai · Claude Code · CodexDefines the target commit, build and migration order, environment, smoke tests, observation and rollback.
auditing-product-securityDownload skill (.zip)Claude.ai · Claude Code · CodexReviews secrets, trust boundaries, authentication, authorisation, RLS, public endpoints, prompt injection, dependencies and deployment.
assessing-ai-data-protectionDownload skill (.zip)Claude.ai · Claude Code · CodexExamines purpose, minimisation, data flows, vendors, retention, international transfers, DPIA triggers and human safeguards.
designing-operational-observabilityDownload skill (.zip)Claude.ai · Claude Code · CodexConnects user journeys, application health, AI calls, data changes and business outcomes to logs, metrics and alerting.
planning-backup-recoveryDownload skill (.zip)Claude.ai · Claude Code · CodexPlans backup and restore for databases, files and runtime configuration, including RPO/RTO and restoration tests.
reviewing-public-demosDownload skill (.zip)Claude.ai · Claude Code · CodexIsolates a demo from production data and credentials, checking direct URLs, search, exports and client bundles.
reviewing-product-ux-accessibilityDownload skill (.zip)Claude.ai · Claude Code · CodexReviews not only visual polish but journey clarity, keyboard use, focus, forms, mobile behaviour and resilient states.
coordinating-product-incidentsDownload skill (.zip)Claude.ai · Claude Code · CodexCoordinates containment, evidence, communication, recovery and follow-up for outages, exposure or incorrect decisions.
A folder of working instructions for an AI agent. It provides a repeatable process but does not grant additional permissions.
Ways to restrict access by individual data records and by user role.
A test set, the starting result used for comparison, and the minimum conditions a change must meet before release.
A safe alternative path and meaningful review of the result by a person.
A short check of critical functions after release and a prepared way to return to a working version.
Acceptable data loss, acceptable recovery time, and an assessment of how data processing may affect people’s rights and freedoms.
Back up any custom edits, then replace only the relevant skill folders. Codex normally detects changes automatically; Claude Code watches SKILL.md changes. Start a new session if discovery appears stale.
Delete the specific skill folder from ~/.agents/skills or ~/.claude/skills. Do not delete the parent directory, as it may contain other skills.
To avoid duplicate files, advanced users may keep skills in one directory and use symbolic links. Confirm symlink support in your current tool version first.
Project skills can be stored in Git. Review changes as you would code: an instruction can alter the agent’s decisions, scope and proposed commands.
SKILL.md and its supporting files before installation, especially when the package comes from a third party.build-skills.js for reproducible authoring. The script makes no external connections and is not needed for normal installation: only the contents of skills are copied. The packages contain no passwords, API keys or production data.agents/openai.yaml contains Codex interface metadata. Claude Code may ignore it; SKILL.md is the skill entry point.