Handle operational requests from Slack threads across a database, Stripe, Linear, and GitHub. The skill guides lookups, issue creation, and PR reviews while defining platform access limits and human approval requirements for consequential changes.
中文简介正在准备中。当前显示英语简介。
Cross-platform operations runbook for the Slack control-pane agent. Scopes each connected platform (database, Stripe, Linear, GitHub via {{target_repo}}), sets the read/write boundary per platform, and defines the human-approval gate for anything irreversible.
安装前可以查看交给 AI 代理的指令内容。
Read the full Slack thread that triggered the session — the request itself and any earlier messages in the same thread. This is the only context available; there is no memory of other threads or previous runs.
Work out which connected platforms the request touches before doing anything:
| Platform | Access | Typical read | Typical write |
|---|---|---|---|
| Database | Read-only via scoped DATABASE_URL | Account/plan lookups, counts, joins | Not possible with this credential — the role cannot run UPDATE/DELETE/ALTER or any schema-changing statement. Surface the exact change needed and hand it to a human to run directly, or route it through an approval-gated connector/tool that supports it |
| Stripe | Composio connector (brokered) | Plan, invoices, subscription status | Refund, plan change, cancellation — approval gate |
| Linear | Composio connector (brokered) | Search issues/projects | Invite a member, create a project or issue — safe to do directly |
| GitHub | gh CLI + GH_TOKEN against {{target_repo}} | View/diff a PR, read issues and checks | Review, comment, and open a PR freely — never merge |
| Sandbox | Built-in to the session | — | Spin up an ad hoc sandbox to reproduce a bug or run a one-off script — always disposable, always safe |
For anything that isn't a pure lookup, gather the facts first: read the relevant database rows, the customer's Stripe state, the existing Linear issues, and the GitHub PR/diff/checks. Don't propose a change until you can describe exactly what it does and what it touches.
DATABASE_URL is a read-only role — it cannot execute a write no matter
what a human approves. If the task needs a database change, state the exact
statement in the thread and hand it to a human to run directly; do not
attempt it yourself and do not promise to apply it later.gh pr view, gh pr diff, gh pr checks, gh issue view to
review. When a fix is warranted: branch, commit, and
gh pr create --repo {{target_repo}}. Opening a PR is fine — merging is not.Post the exact action you're about to take — the platform, the specific
change, and its effect — and wait for an explicit reply in the thread before
acting. In a channel, ask the approver to @mention the bot, or the reply never
reaches you. Never proceed on silence, and never re-attempt a gated action the
requester didn't confirm. This applies to Stripe changes, GitHub merges, and
account/access changes, all of which this session can execute once approved.
Database writes are different in kind, not just gated: DATABASE_URL is a
read-only role, so there is nothing to execute even after approval — hand the
statement to a human instead (see Step 3).
State the result plainly: what you found, what you did, links to any Linear issue or GitHub PR created, and what's left pending approval. This thread is the only output channel for the task.
{{cadence}})This run is not a task — no Slack thread triggered it. Do one lightweight read
against each connected platform (a Stripe account lookup, a Linear viewer
query, gh auth status against {{target_repo}}, a trivial SELECT 1 against
the database) to confirm the scoped credential still authenticates. Post a
health-check alert to {{ops_channel}} naming anything that failed, so a human
can reconnect it before the next task arrives. Do nothing else on this run.
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Review Slack access requests against Okta role and team information, then prepare narrowly scoped GitHub or AWS IAM permissions. Apply changes only after an eligible person's approval and record the grant, reasoning, approver, and timestamp.
中文简介正在准备中。当前显示英语简介。
Research companies and people before outreach or meetings. Combines business profiles, recent news, hiring signals, and key contacts into a sourced brief with talking points and suggested questions, adding relationship history when CRM data is connected.
中文简介正在准备中。当前显示英语简介。
Review daily Google Ads and Meta Ads results for budget pacing, declining performance, and unusual activity. Get prioritized findings with supporting numbers and concrete recommendations for a marketing team to assess and carry out.
中文简介正在准备中。当前显示英语简介。
Automate website tasks such as navigating pages, filling forms, clicking buttons, taking screenshots, and extracting data. The skill also supports web app testing, with specialized guides for Electron desktop apps, Slack, and cloud browsers.
中文简介正在准备中。当前显示英语简介。
Process emailed vendor invoices by extracting details, comparing them with purchase orders and invoice history, and recording duplicates, overcharges, or missing orders. Summarize results in Slack for human review; payment approval and execution remain with people.
中文简介正在准备中。当前显示英语简介。
Guide changes to Kortix billing code, admin controls, and pricing screens. Explain how plans, trials, enterprise contracts, and access exceptions should work, where pricing is defined, and which audited routes must handle account changes.
中文简介正在准备中。当前显示英语简介。