Loading...
Loading...
Found 204 Skills
Lightweight session memory CLI for agent workflows. Provides persistent journal, artifact, task, state, idea, and debug tracking across sessions and conversation compaction.
Create, inspect, validate, explain, and improve Ralph hat collections. Use this skill whenever the user asks to make or refine a `.ralph/hats/*.yml` workflow, debug hat routing, explain event topology, or tune a multi-hat Ralph run.
Gitlab integration. Manage Projects, Groups, Users, Labels. Use when the user wants to interact with Gitlab data.
Manage document verification and review workflows in Glean. Use when verifying document accuracy, listing pending verifications, or sending review reminders.
SuprSend CLI is a command-line interface tool for managing your SuprSend account and resources. It provides a convenient way to interact with the SuprSend API, allowing you to perform various operations such as managing workspaces, users, workflow, templates and more.
Implements Syncfusion WinUI Kanban (SfKanban) control for workflow visualization and task management. Use this when building Kanban boards, agile project tracking, or workflow management systems in WinUI applications. This skill covers cards, columns, swim lanes, WIP limits, drag-and-drop, workflows, sorting, events, and customization.
Break down complex tasks into three layers: Dao, Shu, Fa, integrating Confucianism, Taoism, Mind Learning, and Art of War to first set the situation, main path, and first-move advantage
Write or update external guide documents for the project —— dev-guide (for contributors / integrators / downstream developers) and user-guide (for end users). The output is stored in the project's docs/ directory, maintained alongside the code, and searchable by search tools. Difference from libdoc: guidedoc is task-oriented ("How to do Y with X"), while libdoc is reference-oriented ("What each part of X looks like"). Trigger scenarios: When the user says "write documentation", "developer guide", "user guide", or proactively push when feature-acceptance is completed.
Shows a structured progress dashboard for an album with percentage complete per phase, blocking items, and status breakdown. Use for a quick visual overview of album progress.
Full optimization workflow, sub-agent launch templates, agent communication contracts, default configurations, tuning strategy, and knowledge base update protocol. Use when: (1) starting an optimization cycle, (2) launching a Profiler or Designer sub-agent, (3) interpreting or formatting agent communication, (4) updating the knowledge base after a profiling or implementation iteration, (5) deciding default configurations or tuning strategy for a kernel.
Propose a change with optional working artifacts. Use when the user wants a structured proposal with design notes, tasks, and a clear path to implementation.
When developing new features, follow this sub-process — take the vague idea of "add X capability" through to the acceptance closure, with solution documents archived so that both AI and users can later check the original thinking and decision rationale. Trigger scenarios are focused on adding new capabilities ("develop new feature", "add X", "implement XX"), and do not handle bugs in existing code. This skill only acts as a router, deciding which sub-skill to trigger next among brainstorm / design / fastforward / implement / acceptance based on existing artifacts.