Loading...
Loading...
Found 373 Skills
红琥珀警示 deck — 顶/底 45° 红黑 hazard 条纹、红色删除线否定标题、L1/L2/L3 绿/琥珀/红 tier 卡片、圆点状态 alert box、policy-yaml 代码块（红左边框 + bad 关键词高亮）、红绿 checklist、Q1 事故堆叠柱状图。适合安全 / 风险 / 事故复盘 / 红队 / 上线前 AI 评审 / policy-as-code。
Plan and execute a launch runbook covering pre-launch verification, go-live procedures, DNS cutover, post-launch monitoring, and rollback procedures. Use this skill whenever the user is preparing to launch a website or product, planning a DNS cutover, building a go-live checklist, or executing a launch day. Triggers on launch runbook, go-live, launch day, DNS cutover, deploy to production, site launch, product launch, cutover plan, launch checklist, deployment procedure. Also triggers when a launch is approaching and the team needs structured coordination, even if 'runbook' is not explicitly stated.
The operational playbook for launching a feature well. Positioning, internal alignment, customer comms, sales enablement, support readiness, rollout strategy, monitoring with pre-defined rollback triggers, post-launch measurement against spec hypotheses, and the discipline that distinguishes shipping from releasing from actually launching. Triggers on launch plan, feature launch, launch checklist, ship vs release, rollout strategy, gradual rollout, sales enablement, support readiness, launch announcement, post-launch measurement, launch failure, declared victory too early. Also triggers when planning a launch (any size, any segment), auditing an existing launch process, fixing the we shipped it but the metric did not move problem, or building a launch checklist for the team.
Prepare a structured, scannable review checklist for a branch or diff, grouped by feature change and applying the four-pass review order (Types, Data Flow, Business Logic, Edge Cases) within each feature. Use when the user asks to "prep a review", "review order", or wants a checklist to manually walk through changes.
What's blocking close — maintain the closing checklist with status, critical path, and days to close. Self-updating: ingests new items from diligence findings and schedule builds, tracks status, surfaces what's blocking. Use when user says "closing checklist", "what's left to close", "checklist status", "add to the checklist", or on a scheduled status pull.
Use when preparing ANY app for App Store submission - enforces pre-flight checklist, rejection prevention, privacy compliance, and metadata completeness to prevent common App Store rejections
Use when you need to execute R3 (Prototype Generation) in the product requirement Spec process of sdlc-dev, generate requirements/prototype.md based on requirements/prd.md (including task flow + page structure + ASCII wireframe + AC mapping + walkthrough script), and avoid proceeding with generation without context/PRD, using Open Questions instead of verification checklists, or using non-ASCII formats that make the prototype untraceable and unreviewable.
Use this skill when diagnosing, configuring, or monitoring NICs for AF_XDP / XDP workloads. Covers driver detection, hardware queue configuration, offload control (GSO/GRO/TSO/LRO), VLAN offloads, Flow Director (FDIR) rules, CPU core pinning and NUMA awareness, hardware queue and drop monitoring, BPF program inspection with bpftool, kernel tracing via ftrace, perf profiling and flamegraphs, IRQ-to-queue-to-core mapping, and a quick diagnostic checklist.
Comprehensive go-to-market strategy and launch execution skill. Use when planning a product launch, feature announcement, market entry, or release strategy. Activates for: go to market, GTM, product launch, launch strategy, launch plan, launch execution, launch marketing, GTM playbook, launch readiness, technical launch, beta launch, early access, waitlist, Product Hunt, feature release, announcement, how do I launch this, launch checklist, we're about to ship, market entry, startup GTM, PLG vs sales-led, GTM motion, launch marketing pack, press outreach, developer product launch.
Generate an onboarding checklist and first-week plan for a new hire. Use when someone has a start date coming up, building the pre-start task list (accounts, equipment, buddy), scheduling Day 1 and Week 1, or setting 30/60/90-day goals for a new team member.
Privacy-first planning-only statement export for banks, cards, brokerages, and payment platforms. The LLM builds a manual download checklist with official URLs, suggested date ranges, export formats, and staging directory, but does not use browser tools or browser automation. Use when account files are not on disk yet and the user wants more privacy. CLEAR step: C (Capture)
Use when preparing your agent for production — IAM scoping, inbound auth (JWT, SigV4), secrets management, cold start optimization, session lifecycle, rate limiting, input validation, and quota guidance. Triggers on: "production checklist", "harden agent", "production ready", "secure agent", "inbound auth", "going live", "cold start optimization", "session lifecycle", "StopRuntimeSession", "quota", "throttling", "maxVms", "rate limit", "security audit of outbound API calls", "gateway target audit for production", "restrict who can call", "lock down endpoint", "only our app can call". Not for Cedar tool-restriction policies — use agents-connect. Not for quality measurement — use agents-optimize. Not for outbound credential storage or API key wiring — use agents-connect. Not for A2A agent-to-agent auth — use agents-build. Cold start observation and diagnosis (not optimization) routes to agents-debug.