Results for “question”

Embody the voice and methodology of Aaron T. Beck, founder of CBT, to guide users through cognitive restructuring techniques like thought records and behavioral experiments.

Writes Alan Hirsch's 8-week transformational course content, including video scripts, readings, case studies, reflection questions, and field experiments, in his voice with formation-over-information pedagogy.

Extract false-positive and false-negative gaps from VLM binary-classification-question predictions by comparing model responses against ground truth, producing a structured JSONL file and summary report for downstream root-cause analysis.

Index and router for a C-level advisory bundle of 33 skills covering 14 C-suite roles, orchestration, cross-cutting capabilities, and culture. Use to explore the bundle, decide which advisor skill fits a question, or find entry points like the onboard interview, chief-of-staff routing, and board-meeting protocol.

Turn a keyword or topic plus an audience into a writer-ready brief a writer can act on without a meeting. Nails the search intent, the angle, the outline, the must-cover questions, the internal links, and the one CTA. Trigger on "write a content brief", "brief this article", "what should this post cover", "outline a post on", "give my writer a brief for", or "plan an article about".

Captures and organizes chaotic brain dumps into a structured, actionable system with zero information loss. Use this skill whenever the user says 'capture this', 'brain dump', 'let me dump some ideas', 'I've got a bunch of thoughts', 'here's everything on my mind', 'idea dump', 'let me get this out of my head', 'I need to organize my thoughts', 'here's what I'm thinking', or any variation where someone is unloading a messy stream of ideas, tasks, thoughts, and plans wanting them turned into something coherent. Also trigger when the user pastes or dictates a long, unstructured block of mixed ideas — even without the exact phrase — the intent is the same. Fast-to-action by design: no upfront intake. Output is four sections (Projects/Ideas, Tasks, Connections, How I Can Help) ending with a directive question. Asks at most one mid-organization clarifying question when a single item is genuinely ambiguous between task and project.

Local CLI issue tracker for todos, follow-ups, structured records, and the canonical pattern for decomposing multi-step work into a parent + subissues with acceptance criteria, dependency edges, and priority. Use when the user mentions a task to remember, a bug to track, an open question, anything that needs to outlive the current turn, or when planning multi-heartbeat work that needs `chainlink issue ready`-driven pickup across sessions. Includes guidance on writing descriptions future-you can act on (handles, success path, failure path) and idempotency tactics for actions that might fire twice (boundary firing, overlapping heartbeats, retried subagent completion). Pairs with five-whys (chainlink is the storage backend for RCA trees). Storage is local — issues live under a `.chainlink/` directory in the operator's repo.