Productivity

cdeistopened Skill

Reference for creating Obsidian .base files — built-in database views that query vault files by frontmatter properties. Use when creating task dashboards, content indexes, filtered views, or any structured data display in Obsidian.

cdeistopened Skill

Interactive onboarding guide that helps new Claude users (Desktop or Code) discover their highest-leverage AI workflows. Interviews them about their job, tools, and processes, then sets up integrations, installs relevant skills, and identifies workflow automation opportunities. Use when someone is getting started with Claude or wants to get more out of it.

cdeistopened Skill

Write sales copy (emails, landing pages, CTAs, subject lines) that sounds like the creator — not a marketer. Merges 6 direct response frameworks (Schwartz, Hormozi, Chaperon, Dean Jackson, Halbert, Bencivenga) invisibly into the creator's natural voice. Use when writing course launches, email sequences, sales pages, pop-ups, social captions, re-engagement emails, or any commercial content for a creator or brand. Requires a voice reference (voice-dna or style guide).

cdeistopened Bundle

Produce podcast episodes from Notion transcript to a single editor handoff document. Three phases with two human decision points.

cdeistopened Skill

Extract clips from YouTube videos — download full-resolution video, identify compelling moments from transcripts, cut clips with ffmpeg (lossless, with editorial padding), and generate platform-optimized on-screen text and captions. Use when the user says "cut clips", "extract clips", "pull clips from this video", "find the best moments", "clip this interview", or has a YouTube URL they want to turn into short-form content. Also use when re-cutting or adding clips to an existing set, or when someone has a transcript and wants to identify clip-worthy moments even without a video yet.

practice019 Bundle

Define 阶段：写代码前先把要做什么讲清楚，产出规格（对应 /spec）。当新项目/新功能启动、需求模糊、或用户想要规格先行的工作流时使用。 Define phase: clarify what to build before writing code. Use when starting a new project/feature, requirements are vague, or the user wants a spec-first workflow (equivalent to /spec).

dinglebear-ai Bundle

Use when addressing GitHub pull request review comments systematically with mandatory resolution tracking. Triggers on "address PR comments", "fix review feedback", "handle PR review", "resolve PR threads", "respond to review", "work through comments", "mark threads resolved", or any mention of systematically handling GitHub PR review feedback. Fetches comments via gh CLI, creates beads for each thread, presents a grouped summary, links commits to review threads, closes beads on resolution, and blocks completion if unresolved threads remain. Use proactively whenever the user is working through PR feedback — even if they don't explicitly ask for the full workflow.

dinglebear-ai Bundle

Deprecated compatibility alias for log-code-session. Use when an existing workflow or user still says "save-to-md" or "/save-to-md". Delegate the complete request and arguments to log-code-session, which writes the coding-session artifact without committing, pushing, merging, tracker mutation, or repository cleanup. Prefer log-code-session or wrap-session for all new workflows.

dinglebear-ai Bundle

Use when managing calendars or contacts on a self-hosted Radicale CalDAV/CardDAV server. Trigger for requests such as "list my calendar", "what's on my calendar this week", "when is my next event", "add to my calendar", "create an event", "schedule a meeting", "cancel an event", "find a contact", "what's someone's email", "search my contacts", "add a contact", or mentions of Radicale, CalDAV, CardDAV, calendar events, addressbooks, or contact management.

dinglebear-ai Bundle

Create a reusable, evidence-backed homelab or development runbook from a proven procedure. Use when the user says "create a runbook", "turn this into a runbook", "document how to do this again", "write a recovery procedure", or asks for a repeatable operational workflow. Read related maintenance logs, session logs, decisions, standards, and current configuration before writing. This skill writes the runbook only and never executes the procedure or publishes the artifact.

dinglebear-ai Bundle

Use this BEFORE creating a git worktree or implementing any plan. Tailored to our workflow — prefer it over superpowers:using-git-worktrees and every other worktree skill. Triggers - creating or adding a worktree; starting lavra-work, lavra-work-ralph, lavra-work-teams, executing-plans, subagent-driven-development, or work-it; whenever a Claude, Codex, or Gemini plan mode is entered or a plan is accepted; or before implementing anything in a fresh branch. Creates the worktree under .worktrees/ in the repo and makes it identical to and as warm as the main checkout - copying secrets and local config (.env, CLAUDE.md.local, .claude/settings.local.json), symlinking warm caches (node_modules, .venv, target, .next), and re-trusting mise/direnv. Also use when a worktree is missing files, builds cold, or reports mise 'not a trusted directory'. Bundles a worktree-sync engine, a create-in-.worktrees entrypoint, a minimal baseline template, and references.

kai-cli Bundle

Spec-driven development accelerator for turning ideas into specs, plans, task lists, implementations, and validation loops. USE WHEN speckit, spec kit, specification kit, write a spec, create a plan from a spec, derive tasks, implement from tasks, spec-driven development, clarify requirements, validate a plan against a spec.

zereight Bundle

Q&A extraction workflow. Use for turning articles, books, papers into question-answer chains, 질문 뽑기, Q&A 정리.

zereight Bundle

Content card and visual export workflow. Use for PNG cards, infographics, comic cards, whiteboard visuals, 카드로 만들어줘, 이미지로 정리, 정보그래픽, 만화 카드, 화이트보드.

zereight Bundle

Core driver analysis workflow. Use for finding first principles, independent factors, 핵심 요인, 구조 분석, first principles.

zereight Skill

Reading companion workflow. Use for books, essays, articles, close reading, 같이 읽기, 독해, text walkthrough.

zereight Skill

Concept learning and explanation workflow. Use for concept breakdown, learning, 개념 설명, 쉽게 이해, 공부 도와줘.

zereight Skill

Plain language rewriting workflow. Use for simplify, explain like I am smart but new, 쉽게 풀어줘, 번역투 제거, 쉬운 설명.

zereight Skill

Deep thinking workflow. Use for root-cause thinking, why analysis, 본질 분석, 깊게 생각, drill down.

zereight Skill

Investment analysis workflow. Use for startup, token, stock, product, market, 투자 분석, 사업성 검토, 프로젝트 분석.

zereight Skill

Writing workflow for developing an idea into an essay. Use for essay draft, argument writing, 글쓰기, 초안, 생각 정리.

zereight Bundle

Cost-aware Chorus review workflow for explicit review requests only. Use only when the user explicitly invokes `$chorus-review`, says `chorus-review`, or asks to review with Chorus. Routes review work through a Claude-optional, Codex xhigh, Gemini review profile; preserves normal Codex low reasoning outside review; checks Claude health before use; avoids spending Claude/Codex quota unless this skill was explicitly requested.

zereight Bundle

Skill map and inventory workflow. Use for scanning installed skills, skill overview, 스킬 목록, skill map.

zereight Skill

Paper workflow combining reading and card creation. Use for paper summary plus visual card, 논문 읽고 카드, paper to card.

zereight Bundle

Structured roundtable discussion workflow. Use for multi-perspective debate, panel discussion, 관점 토론, 라운드테이블.

zereight Skill

Relationship analysis workflow. Use for interpersonal patterns, conflict, conversation, 관계 고민, 대화 분석.

swestash Bundle

Write commit messages, PR descriptions, and manage branching strategy following conventional commits.

swestash Bundle

Orchestrator and entry point for the swe-workflow skills library — consult FIRST when starting any non-trivial software task; most skills load name-only and only activate when invoked here. Routes intent to the right skill(s) and invokes them by name; shows the Golden Path chains.

swestash Bundle

Guide test-driven development with red-green-refactor. For NEW code via test-first — use test-suite-design for adding tests to existing code.

pproenca Skill

Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for /arena, 'arena this', 'throw it in the arena', or when one attempt at a non-trivial artifact would lock in the wrong shape.

pproenca Bundle

Apply when existing behavior is WRONG in a bounded, specific way and must change in one place — a bug, defect, incorrect output, off-by-one, mishandled edge case, regression. Use this whenever the task is "fix the bug where...", "X is broken", "wrong result when...", "handle this edge case". The dominant failure mode is RECURRENCE (the bug comes back) or breaking a NEIGHBOR, so the rule is: write a FAILING repro test that captures the bug (RED) BEFORE the fix, make it pass (GREEN), and leave it as a permanent regression lock. This is the fix instance of the one-spine change loop in feature-workflow; it delegates to that skill's change_new.py/change_check.py/verify.py with --kind fix. Do NOT use for new behavior (feature-workflow), behavior-preserving restructuring (refactor-workflow), or approach-unknown problems (spike-workflow). If a "fix" keeps growing in scope, it is a feature or a refactor — reclassify at STEP 0.

pproenca Bundle

Run this FIRST when installing or onboarding the boundary-discipline, feature-workflow, and verify-and-diagnose skills into a repository. It establishes and validates boundary.config.json — the shared config every one of those skills' scripts (scan, shelf_index, promote, verify) reads to learn this repo's conventions: which directories map to which substrate layer, the file extensions, the feature roots, and the verify-gate check commands. Use this whenever setting up the skills in a new repo, when boundary.config.json is missing or stale, when the harness scripts return empty or clearly wrong results (a symptom of misconfiguration), or when the repo's structure has changed. The config is the trust boundary of the whole harness — this skill is how you parse it once, correctly, so every later stage can assume it. Detect, propose, confirm with the human, validate, record.

pproenca Bundle

Apply when changing the STRUCTURE of code while preserving its observable behavior exactly — extracting a unit, renaming, reshaping a module, splitting a god-function, moving a boundary, detangling coupling. Use this whenever the task is "refactor X", "clean up", "extract", "restructure", "detangle", or "preserve behavior but change how it is organized". The dominant failure mode is SILENT REGRESSION, so the rule is: capture a GREEN characterization net that pins current behavior BEFORE touching anything, change under that net, and prove behavior is identical after. This is the refactor instance of the one-spine change loop in feature-workflow; it delegates to that skill's change_new.py/change_check.py/verify.py gate-runners with --kind refactor. Do NOT use for new behavior (feature-workflow), bug fixes (fix-workflow), or approach-unknown problems (spike-workflow). For a boundary-level refactor, use boundary-discipline REFACTOR mode as the tool inside this loop.

pproenca Bundle

Full App design workflow — check progress and continue from where you left off

pproenca Skill

This skill is loaded automatically at session start via SessionStart hook. Establishes protocols for finding and using skills, checking skills before tasks, brainstorming before coding, and creating tasks for checklists.

pproenca Bundle

This skill should be used when the user asks to "find the root cause", "trace the bug", "why is this happening", "where does this come from", or when errors occur deep in the call stack. Systematically traces backward to identify the source.