Loading...
Loading...
Found 136 Skills
Selection and writing methods for short-form video hooks (openings), Chinese name: 「钩子」. Use when creating a hook, writing a hook, figuring out how to write a hook, running out of ideas for a hook, designing a hook for the first 5 seconds, or writing a video opening or spoken-script opening; also use when the user asks how to start a video, requests an opening template, asks about hook types, or asks for help creating a hook, including during ra-洗稿 script rewriting and topic ideation. Provides a scenario-based taxonomy of 7 hook types with a decision flow, prerequisites, sentence templates, and common mistakes. To diagnose and optimize an existing hook draft, use dbs-hook instead; this skill chooses the type, while dbs-hook refines the execution.
This skill generates a comprehensive set of Frequently Asked Questions (FAQs) from the course description, course content, learning graphs, concept lists, MicroSims, and glossary terms to help students understand common questions and prepare content for chatbot integration. Use this skill after course description, learning graph, glossary, and at least 30% of chapter content exist.
Use when the user asks to audit a Solana or Anchor codebase, explain report-backed Solana vulnerability classes, review signer or PDA bugs, analyze CPI trust boundaries, assess Token-2022 integrations, digest a public Solana audit report, investigate an exploit path, or generate audit-readiness and release-blocker checklists.
Evolve your brain's schema pack. Add page types, propose new ones from corpus scans, backfill page.type on existing pages, audit pack health. Triggers when an agent notices untyped pages, custom domains needing typed entities (researcher, contract, deposition), or wants to see what types the pack declares.
Coach product managers and produce a PM Coaching Pack (context-specific definition of “good PM”, evidence-based assessment, growth bets + development plan, coaching cadence + session toolkit, follow-up tracker). Use for coaching PMs, developing PMs, leveling expectations, and creating growth plans. Category: Leadership.
Read production traces, identify what's failing, and build failure taxonomies using open coding and axial coding methodology. Use when debugging agent or pipeline quality, investigating "why are my outputs bad?", or before building any evaluator — error analysis must come first. Do NOT use when you already have identified failure modes and need evaluators (use build-evaluator) or datasets (use generate-synthetic-dataset).
Registro, priorización y planificación de deuda técnica: taxonomía, puntuación, informe, integración con sprint.
Design the structure, hierarchy, and navigation model for a product's content and features.
Coach product managers with evidence-based feedback, growth plans, and operating cadence.
Use when starting a session to find work, creating/triaging issues, or completing work and updating issue status
Use when capturing post-mission audit data or analyzing audit records into a findings report with GitHub issue recommendations.
Standardized artifact creation via tk tickets. Use whenever a skill needs to persist output — research findings, plans, postmortems, reviews, design specs, decisions. Replaces all bespoke output directories (.oracle/, .plans/, etc.) with a single canonical system.