26 skills · sorted by relevance
Close out a launched Claude Managed Agent by listing its recorded components and completed phases. Refresh a shareable, self-contained HTML overview and rank the next one or two upgrades from deferred work and operational improvements.
Close out (or revisit) a Claude Managed Agent build — refresh the overview page, recap every primitive the founder now owns, show the run log and live status, suggest 1–2 tailored next upgrades, and sweep hygiene (sessions archived, key only in .env, no literal dates in deployment kickoffs). Use when the founder says "/wrap-up", "wrap up", "close it out", "where do things stand with my agent", or at the end of a /launch-your-agent build.
The English summary is being prepared. Showing the original description.
End-of-session wrap-up. Save what was learned this session to auto-memory, verify the working tree is committed/pushed, and emit a brief resume prompt the user can paste next time. Invoke as /done to close a work session. Wrap-up is auto-memory ONLY — never writes a handoff.md or any handoff file.
The English summary is being prepared. Showing the original description.
Prepare a graded Claude Managed Agent for recurring schedules, event triggers, or on-demand use. Validate timing, build deployment request data, optionally include self-evaluation for each run, and document the next steps in a roadmap.
Plan a Claude Managed Agent around one clear job, then route work through setup, launch preparation, evaluation, and scheduling. Produce execution plans and curl commands that users run with their own Anthropic API key.
Create a customer interview guide focused on past behavior, current problems, and desired outcomes. Adapt questions to research goals and available time, with follow-up prompts and a note-taking template to capture findings consistently.
Test an app idea through focused experiments and collect verified findings for development. It can also suggest what to explore next based on existing experiments and package findings as a reusable project skill.
Explore interface ideas with disposable HTML mockups before implementation. Generate two or three variants to compare, get suggestions for what to explore next, and preserve design findings for future project work.
Build course and workshop slides that keep learning objectives visible on the left. The deck includes concepts with examples, multiple-choice self-check questions, a wrap-up, and a preview of the next module, with warm paper tones and Playfair typography.
Turn validated experiment analysis into an internal research report that supports decisions. Organize findings, statistical evidence, figure interpretations, limitations, and next actions, then save the report as Markdown or write it into a connected Obsidian knowledge base.
Turn completed experiment analyses into an internal research report that explains findings, figures, limitations, and next actions. Reports connect evidence to decisions and can be saved locally or written into a linked Obsidian project.
Write a structured interview guide — warm-up, core exploration, and wrap-up. Use before running interviews. For analysing what comes back, use `summarize-interview`.
The English summary is being prepared. Showing the original description.
End-of-session ritual that audits changes, runs quality checks, captures learnings, and produces a session summary. Use when saying "wrap up", "done for the day", "finish coding", or ending a coding session.
The English summary is being prepared. Showing the original description.
Wrap up a client project the right way — a clean handoff, a strong final impression, and the moves that turn a finished project into referrals and repeat work. Use when asked to wrap up a client project, offboard a client, end a client relationship well, or project handoff. Produces a closeout checklist (deliverables, access, final invoice, documentation), a handoff/wrap-up message, the referral/testimonial/repeat-work asks to make at the peak moment, a graceful process for ending an ongoing relationship, and how to leave the door open — so the ending builds your business instead of just stopping.
The English summary is being prepared. Showing the original description.
Structured persuasion for tech leads, PMs, and founders—not activity logs. Five scenarios (kickoff, status update, wrap-up, investor pitch, solution selling) on one 5-part framework (Hook→Context→Proposal→Evidence→Ask). AI prompts for missing materials and audience context; pre-submit checklist. Claude Code plugin; Cursor, Codex, and chat via prompts.
The English summary is being prepared. Showing the original description.
Create a structured user interview script with warm-up, core exploration, and wrap-up sections. Use when preparing for user research interviews to ensure consistent, insightful conversations.
The English summary is being prepared. Showing the original description.
Package spike findings into a persistent project skill for future build conversations
The English summary is being prepared. Showing the original description.
Package sketch design findings into a persistent project skill for future build conversations
The English summary is being prepared. Showing the original description.
Session wrap-up: consolidates every descriptive markdown file (README.md, AGENTS.md, HANDOFF.md, docs/*) into ONE canonical CLAUDE.md, then reconciles it against the current code state so a fresh session or new teammate can pick up immediately. CLAUDE.md keeps a mandatory PROGRESS block at the top answering two questions: where are we now and what's the next concrete action. Trigger when the user says: "wrap", "wrap up", "/wrap", "tidy docs", "sync docs", "update docs", "archive", "this phase is done", or the Chinese equivalents "收尾", "同步文档", "整理文档", "整理一下", "更新文档", "存档", "梳理一下", "这阶段做完了". A bare "tidy" / "整理" with prior dev context counts. Do not under-trigger.
The English summary is being prepared. Showing the original description.
Cross-tool weekly intelligence briefing that pulls from your calendar, email, Slack, and tasks to produce a comprehensive pulse on what happened and what is coming. Useful for reviewing your week, during end-of-week wrap-ups, for preparing Monday priorities, and when catching up after time away. Use when the user says "weekly pulse", "weekly briefing", "week summary", "what happened this week", "weekly review", or "business pulse".
The English summary is being prepared. Showing the original description.
Walk through the Designer/Developer wrap-up checklist for offboarding a client engagement — conversationally, one item at a time.
The English summary is being prepared. Showing the original description.
Capture learnings from a campaign, launch, sprint, or initiative using Five Whys (Taiichi Ohno, Toyota Production System) for root cause analysis and Start-Stop-Continue for action planning. Append reusable insights to knowledge/learnings.md so future runs of the OS get smarter. Use when the user asks for a retro, retrospective, post-mortem, "what did we learn", "campaign wrap-up", "lessons learned", or after a campaign or launch ends. Critical feedback loop that makes the OS compound over time. For the numbers review itself, see kpi-review. For planning the next campaign, see campaign-brief. For turning a sprint team's retro notes into action items, see retro-synthesizer.
The English summary is being prepared. Showing the original description.
Use this skill when setting up Service Cloud Voice with Amazon Connect — provisioning the contact center, configuring phone numbers, enabling real-time transcription, and configuring After Conversation Work Time. Covers the deployable metadata behind it: CallCenter, ConversationVendorInfo (vendorType), CallCenterRoutingMap, the Voice ServiceChannel that carries ACW, ServicePresenceStatus, PresenceUserConfig, ServiceCloudVoice.settings, and the VoiceCall / VoiceCallRecording objects. Trigger keywords: Service Cloud Voice, Amazon Connect, contact center, softphone, call transcription, After Conversation Work, ACW, wrap-up time, VoiceCall, CallCenter metadata, vendorType, telephony provider. NOT for Omni-Channel routing setup — use admin/omni-channel-routing-setup. NOT for Open CTI softphone adapters — use apex/cti-adapter-development. NOT for Sales Dialer (Voice.settings) — that is a different product.
The English summary is being prepared. Showing the original description.
Commit, push, and open a PR using the cheap low-token git-ops agent. Use for git/github wrap-up — git commit, git push, gh pr create, "ship it", "open a PR", "create the PR", "push and PR", end-of-task git handoff.
The English summary is being prepared. Showing the original description.