bex-co

Autonomously drain a `.pm` workstream — triage every open item (milestone or inbox-note task), then work it to done, park it in `blocked/`, or delete it as invalid, until the workstream has no open items left. Use when the user asks to "loop", drain, or clear…

Analyze and decompose a product topic into a text-only proposal for the repository's .pm board. Use when the user wants to pressure-test scope, size milestones, identify dependencies, or prepare exact PM board commands without writing board files.

Inspect and maintain the repository's .pm workstreams, inbox notes, milestones, and tasks. Use when the user asks for PM board status or requests a supported board mutation such as creating, promoting, adding, or completing work.

Hunt live hosting bugs through the bex CLI against the pinned Render CLI contract, trace failures into server compatibility or the Bex launcher, and file researched, non-duplicate fixes through /pm. Use when asked to QA the CLI or find hosting bugs from…

Drive the live product at https://dashboard.bex.co as a signed-in QA user (QA_EMAIL / QA_PASSWORD from .env or muse.env), hunt real bugs across the hosting features, research each fix down to file:line, file the non-duplicate findings to the w6 board through…

Safely bring main up to date, commit intended pending changes, and push to origin/main — resolving any rebase conflicts autonomously and stopping only when a decision genuinely needs a human. Use when the user explicitly asks to ship the current main branch…

Read a .pm workstream's blocked items, explain the blockers in plain Chinese, guide quick decisions or focused discussion, record the outcomes through pm, and hand implementation to loopx. Use for /unblock wN or requests to help a worker get unblocked; a…

Sets up and configures background workers on bex for queue-based job processing. Use when the user needs to process async jobs, consume from a queue, run Celery/Sidekiq/BullMQ/Asynq/Oban workers, handle graceful shutdown with SIGTERM, wire a worker to Key…

Guide the owner in Chinese through concrete actions and decisions that unblock a .pm worker queue. Use for /unblock wN or requests to help a worker move forward. Recommend what the owner can do next, use a wizard for quick choices or focused discussion for…

Hunt bugs in the Beancount.io remote MCP server by driving the real POST /api-gateway/mcp endpoint with JSON-RPC and real MCP clients, checking transport, discovery, credential boundaries, tool and resource results, the result envelope and prompts against…

Arrange the repository's public .pm adoption board — show status, create workstreams, capture inbox notes, promote notes into milestones, add tasks, mark work done, park blocked work with its unblock condition, and drop work that should no longer be done. Use…

Record bank/card transactions in an existing local Beancount ledger from CSV, OFX/QFX, QIF or PDF statements, including PDF-only banks with no CSV export. For a PDF ledger import, read this SKILL.md before the PDF helper's guide to establish account,…

Record one-off entries the user describes in a local Beancount ledger through bea — a purchase, bill, paycheck, or transfer between their own accounts (including splits and pasted receipt text), opening or closing an account, a price, or a note. Propose the…

Answer explicit requests for facts from a local Beancount ledger using shown, reproducible bea queries and reports for spending, trends, net worth, holdings, subscriptions and anomalies. Do not select this skill merely to gather preliminary inputs for…

Record invoices a business issues and bills it receives in a local Beancount ledger through bea — the receivable or payable for each document with the tax its document states, each payment applied to the document it settles (a processor's gross, fee, and net…

Reconcile one account in a local Beancount ledger against a CSV or PDF statement. For a PDF statement, read this SKILL.md before the PDF helper's guide to establish account comparison, duplicate review and confirmation rules, then use the helper for…

Use for a standard, single-pass security audit of an entire repository or a scoped path, package, folder, or submodule with no diff to review. This is the default repository scan. Do not use for PR, commit, branch, or working-tree diffs, or for deep,…

Use when the user asks for a deep, exhaustive, multi-pass, or variance-reducing repository-wide or scoped-path Codex Security scan. Run repeated complete independent Standard scans with the Codex Security deep-scan tool, which aggregates their validated…

Assess an immutable patch artifact's program impact, regression risk, and auto-merge eligibility. Use for generated patch files, provider pull-request diffs, or commit ranges when reviewers need evidence about affected runtime paths, contracts, tests, and…

Use when Codex is already in the attack-path-analysis phase of a security scan or the user explicitly asks to trace a security finding from source to sink and calibrate severity. Do not use as the primary trigger for full PR, commit, branch, patch, or…

Use when Codex is already in the finding-discovery phase of a security scan or the user explicitly asks to discover candidate security findings in a repository or code change. Do not use as the primary trigger for full PR, commit, branch, patch, or repository…

Develop evidence-backed structural and architectural security hardening proposals from vulnerability disclosures, supplied findings, incident or assessment documents, source code, or a completed Codex Security scan. Use when a user asks for systemic…

Use when Codex is already in the threat-modeling phase of a security scan, the user explicitly invokes $threat-model, or the user explicitly asks to create, update, or persist a repository threat model. Do not use as the primary trigger for full PR, commit,…

Bump, validate, publish, and announce a public @bex-co/bex-security release using upstreamVersion-bex.N. Use only when explicitly asked to cut or publish a Bex Security release.

Release a new version of muse-code-acp to npm through GitHub Actions, including verification, release notes, tagging, and cleanup. Use when asked to release or publish this package.

Autonomously triage and drain a muse-code-acp .pm workstream, verify and archive completion, and ship each resolved milestone. Skip blockers and continue independent milestones. Use for an explicit loopx invocation or a request to work through a whole…

Inspect and maintain muse-code-acp's .pm board, including workstreams, inbox notes, milestones, tasks, completion and evidence-backed drops. Use when asked for board status or a board mutation; not for ordinary code edits or brainstorming without board…

Analyze and decompose a product topic into a text-only proposal for this repository's .pm board. Use to pressure-test scope, size milestones, identify dependencies, or prepare PM commands without writing board files.

Bring main up to date, commit intended pending changes, and push to origin/main, resolving routine rebase conflicts autonomously. Use when the user asks to ship the current main branch or invokes the repository's ship workflow.

Answer or investigate a question without implementing changes. Use when the user invokes dont-code-but-answer or explicitly asks for explanation, diagnosis, or advice without coding or editing files.

Autonomously drain a `.pm` workstream item by item — triage every pending milestone, task, and inbox note, then implement and ship it, close it as already done, block it with an unblock condition, or delete it as invalid, and keep going until nothing…

Propose milestones and tasks for the repository's public .pm roadmap board — decompose a topic through the TPM lens of benchmark trust and adoption, size and gate the work, and emit a text-only proposal for /pm to materialize. Use only when the user…

Arrange the repository's public .pm roadmap board — show status, create workstreams, capture inbox notes, promote notes into milestones, add tasks, mark work done, park blocked work with its unblock condition, and drop work that should no longer be done. Use…

Ship pending changes on master by pulling with rebase, committing intentionally, and pushing to origin/master. Use only when the user explicitly invokes $ship or asks to ship or publish the current master branch.