Loading...
Loading...
Found 10,110 Skills
The always-on protocol for the loam skill namespace. Use at session start and whenever a loam task appears. Routes goals and other loam work, explains the memory model (memory = umbrella; wiki, guidance, and checkpoints are substrates), and lists cross-cutting rules. This is a routing/meta skill — delegate to a specific loam skill rather than performing work itself.
Use when resuming work after a pause, reboot, or context switch and the workspace uses `wiki/checkpoints/` resumable notes. Read the latest relevant checkpoint chain, orient to the most likely in-flight scope, verify current files and tools before acting, and report the safest next step. Treats a goal path as concrete context; checks live goal status over stale checkpoints.
Close the tracker issues that recently merged PRs authoritatively fixed — via `fixes`/`closes`/`resolves` keywords or `closingIssuesReferences` — and post informational comments on issues whose PRs were closed without merging or merged into a non-base branch. Use for post-merge housekeeping and release prep. Respects claim locks and never acts on bare `#N` mentions.
Design and build data presentations — slide decks, board and investor decks, QBRs, analytics readouts, launch and sales decks, conference talks, and interactive web decks — that hold up in a room, in an inbox, and on a phone. Use whenever the user wants slides or a presentation: "make a deck", "turn this into slides", "board deck", "pitch deck", "QBR", "readout", "all-hands", "present these results", "PowerPoint", "pptx", "Google Slides", "keynote", "talk", "webinar", "speaker notes", "slidedoc", "reveal.js", or an interactive/HTML deck — even if they only say "put this in slides" or "we're presenting this Thursday". Covers storyline, slide layout and type specs, staged chart reveals, presenter mechanics, accessibility, and the build path (self-contained HTML, .pptx, Google Slides, or a spec). Composes with dreambase-data-stories, dreambase-visualization-design, dreambase-echarts, and any brand guide, design.md, or .potx the user supplies.
Own the GitHub issue lifecycle with five modes: create issues from a plan or description (kept independent for parallel worktree work), start a `ready` issue into its own worktree, close one out once its PR merges, sync PR↔issue links after merge, and triage the tracker for lifecycle and priority gaps. Use when the user says "create issues from this plan", "file an issue", "start issue #42", "close #42", "wrap up #42 now the PR merged", "sync my issues", "triage the backlog", "prioritize my issues", "set the priority on #42", "issuekit", or wants issues opened, started, landed, reconciled, ranked, or reviewed with the gh CLI.
Route finance questions to an existing local script, a new You.com Finance Research API call, or an MCP payment-aware fallback.
Log a client communication — call, email, text, letter, in-person, voicemail. Append-only per-case record with dated entries, direction, medium, summary, action items. Works alongside /client-letter and /status client. Use when logging a call or client email, reviewing a communication log, or asking "what did we tell [client] last time".
Triage an inbound demand letter — extract fields, cross-check the portfolio, assess merit, present response options with a recommendation, and hand off to matter-intake or demand-intake if escalation is warranted. Use when the user says "we got a demand letter", "triage this demand", or shares an incoming demand to evaluate.
Bridges an Overleaf project to the local skills so a paper kept on Overleaf can be checked, polished, and reviewed, then synced back. Use when a researcher says "my paper is on Overleaf", "sync my Overleaf project", "pull my paper from Overleaf", "run preflight on my Overleaf paper", "edit my Overleaf project locally", or "push my changes back to Overleaf". Walks the three real paths — Overleaf Git integration (clone as a local repo), GitHub synchronization, or download-as-ZIP for free accounts — gets the .tex into a local working copy the other skills operate on, and guides syncing changes back. Treats the Overleaf access token as a secret, never auto-pushes without confirmation, and re-verifies the current Overleaf method live since premium availability and steps change. Trigger words - overleaf, my paper is on overleaf, sync overleaf, pull from overleaf, push to overleaf, edit overleaf locally.
Goal-driven conductor for the whole idea-to-published-paper lifecycle. Takes a research idea plus experiments and a target ("submit to NeurIPS 2026", or "help me pick a venue") and runs a goal->plan->execute->verify->reflect loop. It plans the stages, invokes the right lifecycle skills in order (literature-review, write-abstract, preflight-check, simulate-reviewers, and the rest), checkpoints with the author before each stage, and re-verifies the live CFP via parse-cfp rather than trusting a cached profile. Use when a researcher says "take my idea to a submitted paper", "run the whole pipeline", "orchestrate the paper for venue X", "what's the plan from here", or "what's done and what's next". Copilot, not autonomous author. It stops to ask at every stage gate, never fabricates results or citations, and never submits. Trigger words - orchestrate, pipeline, end to end, whole paper, idea to submission.
Walk through a Data Subject Access Request (or deletion, portability, correction request) and draft the response — verify identity, locate data system-by-system, assess exemptions, draft the acknowledgment and substantive response letters. Use when a DSAR comes in, the user pastes an access/deletion/portability/correction request, or says "DSAR came in", "access request", "right to be forgotten", or "someone wants their data".
Install a community skill from a watched registry. Reads the allowlist first, fetches, shows the RAW SKILL.md (not just a summary), runs structural trust checks, runs skills-qa, and only writes files after explicit user approval. Use when the user says "install [skill]", picks install from browse, or provides a direct skill URL.