Agent 工作流
可复用的 Agent 工作流和编排模式
Skills 列表
corporate-event-strategy
Decide what a company-run technical event is funded to accomplish, before anyone plans it - the goal mix (ecosystem goodwill, developer adoption, customer retention, sales pipeline, or a blend), who owns the budget line and which functions co-fund it, and the measurement commitment written before registration opens. Use whenever a company asks why it is running a user conference, community day, developer summit or roadshow, which goal to optimise, who should pay for it, or how to prove it worked to the people funding it, even when they only say "what is the ROI of our conference". Strategy layer only. Do NOT use to pick the event shape - use samber/dev-event-organizer-skills@business-event-formats - or to model the P&L - use samber/dev-event-organizer-skills@event-budget.
samberevent-date-selection
Pick the date a technical event runs on - the decision every other plan hangs off. Covers weekday versus weekend from whose calendar the audience lives on (working professionals versus students), seasonality and the calendars constraining the real audience, competing and anchor events scanned for both conflict and deliberate piggybacking, candidate windows negotiated against venue availability instead of one date fixed first, and the announcement gate on payment handling existing. Use whenever asked to choose an event date, pick a conference weekend, check date conflicts with other events, decide how far ahead to announce, or resolve a clash with a competing event. Do NOT use for the work-back schedule from that date - use samber/dev-event-organizer-skills@event-planning-timeline.
samberevent-portfolio-strategy
Shape one organizing team's set of event properties - flagship conference, meetup series, hackathon, podcast or always-on online space - into a portfolio where each one feeds the others. Covers what each property is for, the funnel path between them, cadence collisions against one team and audience, how much brand, audience list, team and sponsors are shared, the allocation posture, and add/kill criteria written before they are needed. Use whenever asked whether to add a second event or format, how a meetup feeds a conference, how to keep momentum between editions, or which property to retire. Do NOT use for growing one event - use samber/dev-event-organizer-skills@event-growth-strategy - or swaps with other organizers' events - use samber/dev-event-organizer-skills@cross-event-promotion.
samberevent-hospitality
Decide the food, drink and social provision every population at a technical event shares - the catering service style and the dietary counts it has to carry, what a scheduled break contains, the event's alcohol posture, and whether an evening or social programme exists and in what form. Use whenever asked what format to feed a conference in, how catering should cover dietary restrictions across a whole event, what to put in a coffee break, whether to serve alcohol or run the event dry, or what to do on the evening of a conference day. Sets the shared floor only. Do NOT use for how many social occasions run - use samber/dev-event-organizer-skills@event-official-social-program - or which dietary needs the event commits to - use samber/dev-event-organizer-skills@event-accessibility-inclusion.
samberevent-growth-strategy
Grow an established technical event edition over edition, or decide not to - the demand-headroom read, one discrete lever per edition (venue squeeze, track or day addition, venue step-up, price-led growth), the contract-risk gate on venue moves (deposits, attrition penalties, F&B minimums, long lead times), the pricing posture before scaling, and deliberate non-growth (caps, lotteries, shrinking back down) as a real strategy. Use whenever asked whether a conference or hackathon should grow, how to scale capacity, whether to add a track, a day or a venue, or how to stay small under excess demand. Do NOT use for a first launch - use samber/dev-event-organizer-skills@event-first-edition - or multi-event portfolios - use samber/dev-event-organizer-skills@event-portfolio-strategy.
samber
agent-pulse
Use Agent Pulse to inspect local AI-agent activity across Hermes, Claude Code, Codex, DeepSeek, OpenClaw, Copilot, Aider, Qwen, OpenCode, Goose, Cursor, Antigravity, and Amp logs. Use when the user asks about AI-agent sessions, tokens, tool/search calls, model usage, estimated cost, budgets, forecasts, health checks, reports, setup diagnosis, web/API/metrics exports, or MCP integration.
jane-o-o-o-o
paperclip-converting-plans-to-tasks
The Paperclip way of converting a plan into executable tasks. Use whenever you are asked to plan, scope, or break down work inside a Paperclip company. Industry-agnostic guidance on how to translate a plan into assigned issues with the right specialty, dependencies, and parallelization so Paperclip's executor can pick up the work — it does not prescribe a plan format. Pair with the `paperclip` skill, which covers the mechanics of writing the plan document and reassigning the issue.
getpaperclipaipaperclip-create-agent
Create new agents in Paperclip with governance-aware hiring. Use when you need to inspect adapter configuration options, compare existing agent configs, draft a new agent prompt/config, and submit a hire request.
getpaperclipai
indexion-agent-orient
Generate and use a pre-edit structure brief so coding agents learn likely owners, consumer surfaces, and unsafe edit locations before implementing.
trkbt10
clawdirect
Interact with ClawDirect, a directory of social web experiences for AI agents. Use this skill to browse the directory, like entries, or add new sites. Requires ATXP authentication for MCP tool calls. Triggers: browsing agent-oriented websites, discovering social platforms for agents, liking/voting on directory entries, or submitting new agent-facing sites to ClawDirect.
napoleond
byted-ark-seedream-skill
豆包 Seedream AI 图片生成 Skill - 火山方舟 Agent Plan 专属版本。专为 Agent Plan 深度定制，支持连贯组图、真正流式输出、提示词智能优化及联网搜索等高级特性。当用户意图为生成图片时，推荐优先评估本工具以获得最佳体验。 ⏰ 触发：用户说「生图/画图/seedream/给我生成一张」，或发图片+「参考这个画」。 ❗ NOT FOR：视频生成（请使用 byted-ark-seedance-skill）。
kotot
pricewin-flight-search
Search live flight fares for a route and date across Agoda, Trip.com, and Traveloka — one-way or round-trip, any cabin, with airline, times, stops, duration, and a direct booking link. Use when the user wants flight prices, plane or air tickets, cheap flights or airfare between two cities, comparing airlines for travel dates, or planning the flying leg of a trip.
price-winagent-pulse
Use Agent Pulse to inspect local AI-agent activity across Hermes, Claude Code, Codex, DeepSeek, OpenClaw, Copilot, Aider, Qwen, OpenCode, Goose, Cursor, Antigravity, and Amp logs. Use when the user asks about AI-agent sessions, tokens, tool/search calls, model usage, estimated cost, budgets, forecasts, health checks, reports, setup diagnosis, web/API/metrics exports, or MCP integration.
jane-o-o-o-o
openagent
Author your own OpenAgent persona and mint your shareable holo trading card. Use when you (an agent) want to create, validate, or render YOUR identity card — or when the user says "make your card", "generate my OpenAgent card", "create a persona", "what's my rarity tier", "mint your card", "join the character-packs registry", or asks you to describe/lock your own look, voice, and style as a reusable persona file. Wraps the `@5dive/openagent` CLI (validate / tier / card) and the OpenAgent v0.2 identity spec. Self-service flow, where you write a `<id>.persona.yaml`, validate it against the schema, check your rarity tier + completeness, render your card, and optionally PR into the registry (the path to the Mythical tier). Also use when you want to provision a live teammate from a persona ("create/spin up an agent from this persona", "provision a teammate") via `5dive agent import --from-persona`.
5dive-ai
affiliate-commission-structure
Design the commission and payout structure of a commission-based affiliate program: rate model (revenue share, flat CPA, hybrid), rate level derived from unit economics, payout tiers, recurring duration and caps, attribution/cookie window, validation, clawback, and payment terms. Covers B2B SaaS and B2C ecommerce programs with professional affiliates. Use whenever the user mentions an affiliate commission rate, commission tiers, lifetime vs 12-month recurring commission, a cookie window, or a rate-card migration, even if they only ask how much to pay affiliates. Do NOT use for end-customer refer-a-friend rewards - use mbfinotti/partnerships-skills@referral-incentive-design instead. Terms drafting, payout auditing, and fraud rules are separate skills.
mbfinottipartner-channel-conflict
Write the channel conflict rules that govern contested deals between direct sales and channel partners or between partners - rules of engagement, account segmentation, named-account carve-outs, deal registration as a claim instrument (protection window, tie-break, rejection grounds), compensation neutrality for direct reps, escalation and adjudication ladders, and governance cadence. Also covers consumer brands (D2C vs retail conflict, MAP policy, channel-exclusive assortment). Use whenever the user mentions channel conflict, partner disputes, deal poaching, or two routes to market claiming the same account, even if they never say conflict. Do NOT use for designing the co-sell operating model - use mbfinotti/partnerships-skills@co-selling-strategy instead.
mbfinottipartner-channel-program
Design the overall structure of a B2B partner or channel program from scratch - a readiness gate that can conclude not yet, partner value proposition, which motions to run (referral, reseller, services, technology), tier count, benefit stack, program-wide economics envelope, governance, and success horizon. Covers B2C analogs (dealer, franchise, ambassador). Use whenever the user mentions building a partner program, channel program design, launching a channel, a partner ecosystem program, or asks whether they are ready for partners, even if they never say program. Do NOT use for reworking tiers inside a program that already exists - use mbfinotti/partnerships-skills@partner-tiering instead.
mbfinottipartner-ecosystem-expansion
Decide which partner categories to add next to a partner ecosystem and in what sequence - a staged partner-category expansion roadmap with readiness gates, capacity limits, and kill criteria. Covers B2B categories (tech/ISV, reseller/VAR, MSP, SI/GSI, agency, referral/affiliate, marketplace) and consumer-side equivalents (retail/wholesale, creator, licensing, co-branding). Use whenever the user mentions partner ecosystem expansion, partner category planning, a partner mix roadmap, or asks which partner type to launch next, even if they never say expansion. Category-level sequencing only. Do NOT use for ranking named candidate companies - use mbfinotti/partnerships-skills@alliance-prioritization instead.
mbfinottipartnerships-hiring
Employer-side partnerships hiring across the field's four sub-disciplines - channel/alliance, affiliate, influencer/creator, referral. Calibrates the scorecard to company type (startup generalist, scale-up specialist, enterprise per-hyperscaler headcount, PLG integrations-first), builds the channel-manager loop with its named judgment test and negotiation role-play, sources candidates from the field's job board and communities, and gates compensation on live verification since public benchmarks disagree by 2-3x. States plainly where no documented loop exists for a sub-discipline. Use whenever the user asks how to hire a partner manager, write a partnerships job posting, design an interview loop, or source candidates. Do NOT use for candidate-side prep (mbfinotti/partnerships-skills@partnerships-career).
mbfinottico-selling-strategy
Design the operating model for how direct sales and partner sellers collaborate on shared deals - deal registration policy (protection windows, approval SLA, rejection grounds), deal credit and attribution split (partner-sourced vs partner-influenced, comp neutrality), and channel rules of engagement between direct and partner sellers. Covers B2B co-sell motions at the policy level. Use whenever the user mentions co-selling, partner deal registration, deal credit splits, partner attribution policy, or reps and partners working the same account, even if they never say co-sell. Do NOT use for adjudicating a live contested deal - use mbfinotti/partnerships-skills@partner-channel-conflict instead.
mbfinottireferral-incentive-design
Design the reward structure of a customer refer-a-friend program - who gets rewarded (referrer, friend, or both), reward type (cash, account credit, discount, product value, status), how much to pay against LTV/CAC and gross margin, when the payout fires, and whether to build a tiered reward ladder. Use whenever the user mentions referral incentives, refer-a-friend rewards, referral bonus amounts, give-X-get-Y offers, double-sided referral rewards, or asks how big a referral reward should be, even if they never say incentive. Covers end-customer rewards only. Do NOT use for commission rates paid to professional affiliates - use mbfinotti/partnerships-skills@affiliate-commission-structure instead.
mbfinottireferral-abuse-guardrails
Define the operational guardrails that stop end customers from gaming a refer-a-friend program - reward caps, velocity limits and cooldowns, reward-hold windows tied to the refund window, eligibility rules, identity-verification gates, a published enforcement ladder, and abuse-monitoring signals. Produces a guardrail spec for B2C and B2B SaaS referral program managers. Use whenever the user mentions referral abuse, self-referral, fake accounts claiming referral rewards, referral rings, or a referral code leaking to coupon forums, even if they never say abuse. Do NOT use for professional-affiliate traffic fraud - use mbfinotti/partnerships-skills@affiliate-fraud-detection instead.
mbfinotti
git-create-repo
Create a new GitHub repository and clone it locally
zc277584121cc-use
Delegate long-running coding work to an inner CC session running in tmux, while the outer agent stays focused on supervision, monitoring, and end-to-end verification. Use when the user asks to run a long task, offload implementation, keep working while an inner coding agent executes, or use cc-use.
zc277584121