Loading...
Loading...
Found 8,757 Skills
Use this skill whenever the user wants to work with the Loops CLI from the terminal. This includes installing or updating the CLI, authenticating, storing and selecting API keys, validating credentials, and running commands for contacts, contact properties, lists, events, transactional email, campaigns, email messages, themes, and components. Trigger on phrases like "Loops CLI", "loops auth login", "loops campaigns create", "loops email-messages update", "loops themes list", "loops components get", "loops contacts create", "loops events send", "loops transactional send", "loops api-key", "loops agent-context", "brew install loops-so/tap/loops", or any time the user wants to use Loops from the shell instead of application code.
Use the steipete/summarize CLI to summarize URLs, local files, stdin, YouTube links, podcasts, and media with LLM models. Use when installing or running summarize, configuring provider/API keys, tuning length/language/json/extract/slides flags, setting ~/.summarize/config.json defaults, or troubleshooting CLI errors.
Verify a claim with fresh local evidence: restate it falsifiably, capture baseline and treatment, compare artifacts, and return VERIFIED, NOT VERIFIED, or INCONCLUSIVE.
Use this skill whenever the user asks to read, summarize, review, create, revise, polish, format, preview, or export PowerPoint/PPT/PPTX presentations on Windows, including presentation creation from notes, documents, images, synthesized content, an existing deck, or a template. Use PowerPoint desktop automation through Windows COM for file-producing or editing work, with explicit confirmation before writes. For any new PPT based on documents, PDFs, reports, or synthesized source materials, require a detailed approved Markdown slide plan before producing PPTX unless the user already supplied a sufficient plan. For clear academic paper or literature-presentation tasks, offer optional coordination with nature-paper2ppt.
Scaffold and maintain a reusable research → design → plan → orchestrate → act folder for any non-trivial work — software features, marketing campaigns, org changes. Drops a domain-agnostic spine (00-README · 01-plan · 02/03 research · 04-discussion newest-first · 05-tracking · 09-orchestration · artifact/board.html plan-board) plus stateless action-skills that augment the docs in place without clobbering hand-written prose. Composes ikenga-artifact-builder, huashu-design, frontend-design, ikenga-pkg-builder when present; degrades gracefully when not. Profile-driven: `software` (rich default, code work), `general` (lean, non-code — campaigns, org changes), and `content` (editorial/marketing with key art). TRIGGER when the user asks to start a real plan for non-trivial work ("plan a feature," "scaffold a plan folder," "set up groundwork for…"), references an existing plans/ folder by groundwork structure, or runs any of these actions: groundwork init / research / design / review / clarify / orchestrate / refresh-board / refresh-living-spec / status. DO NOT TRIGGER for one-off code changes, single-document writeups, ADRs, or content that fits in a single markdown file — those don't need a multi-doc plan folder. If the user just wants a single artifact (dashboard, mockup), route to ikenga-artifact-builder instead.
Work a task end-to-end with lean context gathering, implementation, and verification
Start Comment to Fix on HTML — preview with overlay, watch annotations, fix in a loop until stopped. Use when the user runs /comment-to-fix or wants to review HTML slides, proposals, or landing pages with live agent fixes.
Human-in-the-loop safety controls — approval routing via human, LLM judge, or auto-approve with guardrail overrides.
Adaptive multi-agent framework for automated data science tasks with planning, execution, and validation
Use when creating a GitHub pull request or merge request from the current branch, especially when a project PR template may exist.
The orchestrator and entry point for the engineering skills suite. Use this skill whenever the task involves doing engineering work to a high bar — reviewing code or a design, designing a new system or component, debugging a hard problem or running an incident, implementing a substantive change, writing documentation, or sanity-checking an approach. Use it when the user phrases things casually ("rip into this", "be brutal", "is this approach right", "what am I missing", "what would you change", "look at this") or formally ("review this PR", "audit this design"). Use it proactively for any non-trivial engineering work, before declaring something done. The skill triages the work, dispatches to the right specialty skill(s), enforces verification, and produces an evidence-backed result. The goal is to ensure no AI shortcut, sycophantic agreement, or stylistic distraction gets in the way of work that holds up to senior-engineer scrutiny.
Use when driving a website with opencli browser and sitemap context is available, requested, or needed to avoid blind navigation. Guides agents to consume site sitemap files lazily, choose adapter/browser fallback paths, resume from state signatures, and mark stale sitemap entries without trusting them over live browser state.