Loading...
Loading...
Found 35 Skills
Router skill for LLMQuant event workflows. Use when the user needs earnings event briefs, M&A tracking, regulatory risk, catalysts, event calendars, or cross-asset event impact.
Create and manage agent graphs — directed graphs of AI Configs connected by edges with handoff logic. Use when building multi-agent workflows where configs route to each other.
Check project progress, show context, and route to next action (execute or plan). Triggers include "progress".
Enter this sub-process when developing new features — turn the vague idea of "adding X capability" into a closed-loop acceptance process, with solution files archived so that both AI and users can later check what was thought and why decisions were made at that time. Trigger scenarios are focused on new capabilities ("develop new features", "add X", "implement XX") and do not address bugs in existing code. This skill only handles routing, deciding which next step to take among brainstorm / design / fastforward / implement / acceptance based on existing artifacts.
MoAI super agent - unified orchestrator for autonomous development. Routes natural language or explicit subcommands (plan, run, sync, fix, loop, project, feedback) to specialized agents. Use for any development task from planning to deployment.
The root skill of the easysdd workflow family — introduces the workflow system and routes users to the correct sub-skill. Trigger scenarios: Users mention "easysdd", "sdd", "spec-driven", "how to use this set of processes", "which skill should I use", "where to start", or describe a new feature but haven't decided on the entry stage. Known intents (brainstorm/design/implementation/acceptance/BUG/exploration, etc.) will trigger the corresponding sub-skill first instead of this skill.
High-level entry point for cross-platform public social data extraction when the user has not named a platform-specific workflow yet.
Screen incoming NDAs and classify them as GREEN (standard), YELLOW (needs review), or RED (significant issues). Use when a new NDA comes in from sales or business development, when assessing NDA risk level, or when deciding whether an NDA needs full counsel review.
Follow this sub-process when fixing bugs—turn the verbal description of "discovered a problem" into a closed loop of verification and repair, leaving three documents in the middle: issue report, root cause analysis, and repair record. This process adds a buffer between "seeing the problem" and "starting to modify code", avoiding several common pitfalls: the problem description in your mind disappears after modification, fixing only the surface without analyzing the root cause, uncontrollable expansion of repair scope that cannot be traced, and not knowing if the fix is correct without verification after modification. This skill only acts as a router, deciding which of report / analyze / fix to proceed with based on existing outputs. For simple problems that can be identified at a glance, a fast track will be taken, skipping the two middle steps and only keeping the fix-note.
TOC router for PyGraphistry tasks. Use when a request involves PyGraphistry and you need to choose the right workflow: loading/ETL shaping, visualization/layout/sharing, GFQL queries (Cypher, chain-lists, Let/DAG, GRAPH constructors), AI/UMAP/embed/semantic-search workflows, or connector-specific ingestion.
Riffrec product-feedback workflow. ALWAYS load when the user posts a `riffrec-*.zip`, a bundle with `session.json` + `events.json` + `recording.webm` + `voice.webm`, a video/audio recording for product feedback, or asks how to capture and share Riffrec sessions. Routes between setup, quick bug report, and extensive analysis.
Entry point for ALL work requests - triages scope from trivial to massive, asks clarifying questions, and routes to appropriate planning skills. Use this when receiving any new work request.