菜单
Use this skill when managing API access based on billing status. Trigger when: a tenant's trial expires, a payment fails, a tenant upgrades to paid, a suspension is requested, or a resume is requested. The billing gate controls API access but never destroys tenant data.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | billing-api-gate |
| description | Use this skill when managing API access based on billing status. Trigger when: a tenant's trial expires, a payment fails, a tenant upgrades to paid, a suspension is requested, or a resume is requested. The billing gate controls API access but never destroys tenant data. |
The billing gate is the enforcement layer between payment status and Pi API access. It is the only mechanism that disables or restores tenant API access. It never touches tenant memory.
[trial_active] ──trial_expires──> [trial_expired]
[trial_active] ──payment_received──> [active_paid]
[trial_expired] ──payment_received──> [active_paid]
[active_paid] ──payment_failed──> [suspended]
[suspended] ──payment_received──> [active_paid]
[active_paid] ──human_suspend──> [suspended]
[suspended] ──human_resume──> [active_paid]
| State | API Access | Memory | Lead Capture |
|---|---|---|---|
| trial_active | Full | Full | Full |
| trial_expired | Disabled (403) | Preserved | Chat disabled |
| active_paid | Full | Full | Full |
| suspended | Disabled (403) | Preserved | Chat disabled |
--approved-by in the CLI or a signed action in the UI.factoryctl api suspend --tenant <slug> --reason "trial_expired" --approved-by "billing-automation"
factoryctl api resume --tenant <slug> --approved-by "ops@paulipipeline.com"
POST /v1/tenants/{tenant_id}/suspend
POST /v1/tenants/{tenant_id}/resume
Use this skill when generating an interactive educational HTML course from a codebase so that non-technical operators can understand the system. Trigger when: onboarding a new client to their backend, explaining the factory pipeline to an operator, generating operator documentation from source code, or creating visual system walkthroughs.
Use this skill when managing the directory listing, lead capture, lead scoring, lead routing, or consent controls for a tenant. The directory is the trust hook — it gives potential clients a free listing and a discoverable landing page that generates inbound leads. Trigger when: creating directory listings, capturing form/chat/call leads, scoring leads, routing leads to the business, or managing consent and spam controls.
Use this skill when managing org structure, budgets, goals, governance, or agent heartbeats. Paperclip is the business control plane — it does not replace Pi but governs the business that Pi runs inside. Trigger when: creating or updating org charts, setting goals, tracking budgets, registering agents, receiving or sending heartbeats, enforcing human approval gates for business decisions.
Use this skill when executing tenant chat, ingestion, memory reads, skill routing, or API calls on behalf of a tenant. Pi is the backend agent runtime. Trigger when: a tenant message arrives, a document needs ingesting, a skill needs routing, memory needs loading, or any API call targets /v1/tenants/*.
Use this skill when running quality checks on any deliverable before reporting it as complete. Trigger when: finishing a website build, completing a tenant setup, deploying any frontend, committing any code, or generating any operator-facing output. Reject anything that fails the gate.
Use this skill when implementing, extending, or debugging the factoryctl Rust CLI. Trigger when: adding new CLI commands, implementing API client calls in Rust, writing Cargo.toml config, generating CLI help text, implementing the audit runner, or integrating factoryctl with Pi API endpoints.