Loading...
Loading...
Found 5,755 Skills
Build and maintain a Karpathy-style LLM knowledge base — a self-compiling Obsidian markdown wiki where an Agent ingests raw sources, compiles cross-linked concept/entity/summary pages, answers queries against the corpus, lints the graph for health, and audits in-context human feedback filed from Obsidian or the local web viewer. Use when (1) scaffolding a new knowledge base for any research topic, (2) ingesting articles/papers/PDFs/web pages into raw/, (3) compiling or restructuring wiki articles from existing raw material, (4) answering questions against the wiki and filing durable answers back, (5) running lint passes for dead links / orphan pages / coverage gaps / audit shape, (6) processing human feedback from the audit/ directory and applying corrections. Not for general note-taking, daily journals, or non-wiki Obsidian use.
Advantage CSP integration. Manage data, records, and automate workflows. Use when the user wants to interact with Advantage CSP data.
Author step content for Novu workflows defined in the Dashboard or generated/edited via the Novu MCP. Use when filling in step controls (subject, body, editorType, headers, body, conditions) for email, in-app, sms, push, chat, delay, digest, throttle, or HTTP Request steps.
Timekit integration. Manage data, records, and automate workflows. Use when the user wants to interact with Timekit data.
Draft a demand letter from a completed intake, gated on a privilege / FRE 408 / waiver / admission checklist, with a .docx output, post-send checklist, and an offer to create a matter. Use when the user says "draft the demand", "write the [type] letter", or has a finished demand intake ready to turn into a sendable draft.
This skill should be used when the user asks to "research a topic", "run-research", "last30", "what's happening with X", "what are people saying about X", "find the best X", "X prompts", "latest on X", "X news", "what are people recommending for X", "research X for me", or wants to know what's trending, discussed, or debated about any subject in recent weeks.
Generate Harness Service YAML for deployable workloads and create via MCP. Supports Kubernetes, Helm, ECS, Serverless, SSH, and WinRm deployment types with artifact sources from Docker Hub, ECR, GCR, ACR, Nexus, and S3. Use when asked to create a service, define a Kubernetes service, set up a Helm chart deployment, configure an ECS service, or define what gets deployed. Trigger phrases: create service, service definition, Kubernetes service, Helm service, ECS service, deployment service, artifact source.
This skill is strict implementation instruction, not advisory reference text. The skill treats the HTML as discovery-only input, forces interactive Playwright route/state capture, then moves through scored gates for source acceptance, implementation planning, authored UI reproduction, implementation integrity, visual verification, and adversarial proof before signoff.
Especialista em implementação de código no SynkOS. Use esta skill quando o usuário pedir para implementar uma story, desenvolver uma feature, corrigir um bug, escrever testes, refatorar código, ou fazer perguntas como "desenvolva a story X", "implemente o critério de aceite Y", "corrija esse erro", "escreva os testes para Z", "aplique as correções do review". Ative também para entregas técnicas autônomas (modo yolo), para geração de handoff ao finalizar milestones, e para atualização da lista de arquivos modificados em uma story. Não iniciar implementação sem critérios de aceite definidos.
Scaffold the test framework and CI/CD pipeline for the project's engine. Creates the tests/ directory structure, engine-specific test runner configuration, and GitHub Actions workflow. Run once during Technical Setup phase before the first sprint begins.
Investigate why a Duvo Job failed or produced the wrong outcome. Use when the user shares a failed Job, asks "why did this Job fail", or wants to fix a recurring failure on an Assignment. Reads the Job's transcript and the Build that was active for it via the Duvo public API, names the root cause from a fixed failure-mode taxonomy, and proposes one concrete fix — handing off to sop-writer for any SOP rewrite.
Identify inactive/at-risk customers via CRM filters and create follow-up tasks at scale. Builds on `bulk-operations`; defers activity-creation specifics to `sales-execution`.