Loading...
Loading...
Found 1,365 Skills
Ansible integration. Manage data, records, and automate workflows. Use when the user wants to interact with Ansible data.
FIS integration. Manage data, records, and automate workflows. Use when the user wants to interact with FIS data.
Create a GitHub issue in a mitodl repository using the organization's standard issue templates. Triggered by /olissue — prompts for repo, issue type, and fills in the appropriate template (Bug Report, Technical, Product, Design QA). Defaults the organization to mitodl.
Competitor messaging and swipe-file workflow using Meta Ads Library scraping.
CDR Platform integration. Manage data, records, and automate workflows. Use when the user wants to interact with CDR Platform data.
DealerSocket integration. Manage data, records, and automate workflows. Use when the user wants to interact with DealerSocket data.
Agiloft integration. Manage data, records, and automate workflows. Use when the user wants to interact with Agiloft data.
BridgePay Network Solutions integration. Manage data, records, and automate workflows. Use when the user wants to interact with BridgePay Network Solutions data.
Persist learnings to memory or maintain existing memories. Triggers on "extract learnings", "save this for next time", "remember this pattern", "consolidate memories", "dream", "clean up memories".
Comet Phase 5: Archive. Invoke with /comet-archive. Sync delta spec to main spec and archive the change.
Leap integration. Manage Organizations, Pipelines, Projects, Users, Goals, Filters. Use when the user wants to interact with Leap data.
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.