Turn a repeated manual task into a reusable skill you can call by name or schedule. It separates changing inputs from fixed steps, adds approval checkpoints, and tests the workflow against a known result before registration and team sharing.
中文简介正在准备中。当前显示英语简介。
Turns a task the owner keeps doing by hand into a named, reusable skill they can trigger by name or put on a schedule. Watches them do it once or listens to them describe it, works out what varies and what stays fixed, writes the skill with approval checkpoints in the right places, registers it with the router, and shares it with the team. This is how a business gets a workflow nobody shipped for them. Use this whenever the owner describes something repetitive they wish were automatic — including phrasings like "I do this every week," "can you remember how to do this," "make this a thing I can just ask for," "build me an agent," "automate this for me," "turn this into a workflow," or "I want this to happen every Monday." Reach for it when they describe a routine, even without asking for automation.
安装前可以查看交给 AI 代理的指令内容。
Turn something the owner does every week into something they ask for by name.
This is what keeps the plugin from having to ship every industry's workflow. No catalog can cover a septic contractor's permit routine or an insurance agency's carrier commission reconciliation. Those owners can build them.
Two starting points, and the first is much better.
Best: they just did it in this conversation. If the owner has walked through the task with you — pulled the files, made the decisions, corrected you twice — that transcript is the specification. Extract it rather than re-interviewing them. The corrections they made are the most valuable part, because they encode judgment the owner would never have thought to state.
Otherwise: they describe it. Ask them to walk through the last time they did it, concretely. Real specifics beat an abstract description every time — "last Tuesday I pulled the carrier file, matched it against what we'd booked, and chased six discrepancies" tells you more than "I reconcile commissions."
Read reference/capture.md for how to get a complete picture without an interrogation.
This is the whole craft of the step. A skill that hardcodes last Tuesday's specifics only works on last Tuesday.
For each part of the task, decide:
The corrections the owner made while walking through it usually mark the judgment points. When someone says "no, not that one — we skip anything under USD 50," that is a rule. When they say "hmm, depends," that is an approval gate.
Every step that sends, spends, publishes, or deletes needs a gate. So does every step where the owner hesitated.
Do not gate everything — a skill that asks permission nine times is worse than doing it by hand. Gate the consequential and the ambiguous, and let the rest run.
Read reference/skill_authoring.md for where gates belong and how to phrase them.
Produce a real skill in the same shape as everything else in this plugin: a SKILL.md with frontmatter and numbered steps, plus a reference/ folder if the detail warrants it.
Requirements it must meet, same as every shipped skill:
Write it in the owner's terms, not in generic business language. If they call it "the carrier file," the skill says carrier file. A skill full of unfamiliar vocabulary is one they will not trust to run unattended.
Run the new skill against a case the owner already knows the answer to — ideally the exact one they walked through. Show the output next to what they got by hand.
This is the step that determines whether the skill gets used. An owner who has seen it reproduce a known-good result will schedule it. One who hasn't will run it manually and check it every time, which saves nothing.
If it doesn't match, fix the skill and run it again. Do not ask the owner to accept a near-miss.
Add it to smb-router so plain-English requests reach it, and record the trigger phrases the owner actually uses.
If it is a recurring task, offer to schedule it. Scheduling is what converts "a skill I could run" into "something that happens without me," which is the outcome they wanted.
Offer to share with the team. Say what sharing means: who gets it, what data it can reach, and what it can do unattended.
Be specific about the risk when a skill sends, spends, or writes. A skill that emails customers, running for someone who did not build it and does not know its assumptions, is a real hazard. Recommend draft-only for shared skills that send anything.
The owner now has a named skill they can trigger or schedule. If the new skill hit a tool that isn't connected, "connect to my ERP" (build-connector) is the natural next step — it turns the missing system into a working source. Also nearby: "brief me" to fold the new output into the daily picture, and "Monday brief" if the skill should feed the weekly one. Offer at most three, and skip any offer the owner already declined this session.
reference/capture.md — getting a complete picture of the task without an interrogationreference/skill_authoring.md — the structure, frontmatter, and where approval gates belongreference/gotchas.md — the failure modes that produce a skill nobody uses还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Review a design or web page against WCAG 2.1 AA, an accessibility standard. Organize findings on contrast, keyboard access, forms, and screen reader behavior, with severity levels and practical recommendations for fixes.
中文简介正在准备中。当前显示英语简介。
Build a single brief on an existing customer using available sales records, emails, documents, call notes, and internal chat. Understand the current situation, key contacts, recent discussions, and gaps that may need attention.
中文简介正在准备中。当前显示英语简介。
Build or refresh a strategic customer account plan from sales records, emails, and meeting transcripts. Organize goals, stakeholders, growth opportunities, risks, and dated actions into a document, then sync approved highlights to the customer relationship management system.
中文简介正在准备中。当前显示英语简介。
Research prospective companies and contacts, check existing customer records, and assess fit against your ideal customer profile. Receive a sourced brief covering recent developments, likely priorities, outreach talking points, and a suggested next step.
中文简介正在准备中。当前显示英语简介。
Research sales accounts using Common Room data to summarize company details, buying signals, ownership, and key contacts. Answer specific questions directly or prepare a broader briefing with evidence-based next steps, clearly identifying missing information.
中文简介正在准备中。当前显示英语简介。
Score and group accounts by customer fit and engagement, such as recent contact and open sales opportunities. Identify where to focus sales effort, choose next actions, and spot promising accounts with neglected outreach or missing information.
中文简介正在准备中。当前显示英语简介。