Loading...
Loading...
Found 283 Skills
Guides customer-facing and internal technical solution design—discovery and requirements, integration and reference architecture, security/compliance fit, sizing and cost framing, RFP/RFI responses, PoC scoping, build-vs-buy, and handoff to delivery. Use when scoping a customer or partner solution, designing integration architecture for a deal, drafting RFP/RFI technical responses, planning a proof-of-concept, framing security and compliance fit, or preparing solution decks for stakeholders—not for org-wide landing zones and Well-Architected programs (cloud-architect, enterprise-cloud-architect), internal product ADRs and C4 (senior-system-architecture), production Terraform/IaC (infrastructure-engineer), hands-on cloud resource config (cloud-engineer), live PoC execution and competitive demos (sales-engineer), business strategy without technical design (business-consultant), contract redlines (commercial-counsel), or deep FinOps/GL (finops-analyst, compute-accounting-manager).
Mean-variance portfolio optimization via Conjugate Gradient — 40-60× faster than the legacy Neumann path (ADR-126 Phase 3, ADR-123 Wedge 8)
Especialista em pesquisa, análise de dados e gestão do conhecimento no SynkOS. Use esta skill quando o usuário pedir para pesquisar um tema, analisar dados ou evidências, consolidar conhecimento disperso, criar ou atualizar páginas de wiki, documentar achados de discovery, extrair padrões de múltiplas fontes, ou responder perguntas como "o que já sabemos sobre X?", "quais são os riscos de Y?", "pesquise Z e documente". Ative também para auditar a saúde do wiki, promover padrões para memória persistente, ou quando o contexto precisar ser levantado antes de uma decisão técnica ou de produto.
Builds Moran's I spatial autocorrelation workflows in CARTO. Triggers when the user mentions spatial autocorrelation, Moran's I, spatial dependency, spatial correlation, spatial outliers, HH HL LH LL quadrants, high-high clusters, low-low clusters, spatial weight matrix, "is there clustering", "are values spatially correlated", local indicators of spatial association, LISA, spatial randomness test, or wants to determine whether a variable exhibits spatial clustering, dispersion, or randomness across a gridded dataset. Also relevant when the user needs to classify locations into cluster types (HH, HL, LH, LL) rather than just identifying hotspots and coldspots.
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.
Expert guide for the payload-reserve plugin — a Payload CMS 3.x reservation/booking system. Use when working with: reservation systems, booking systems, appointment scheduling, calendar views, availability checks, conflict detection, double-booking prevention, status workflows (pending/confirmed/completed/cancelled/no-show), buffer times, cancellation policies, schedule management, service/resource configuration, customer management, walk-in bookings, or integrating payments (Stripe) and notifications with a Payload CMS reservation plugin. Triggers on: "payload-reserve", "payloadReserve", "reservation plugin", "booking plugin", "appointment plugin", "schedule plugin", "availability overview", "calendar view", "reservation conflict", "double booking", "booking status", "cancellation policy".
Skill B (Visionario) - Product Manager del Escuadrón BLAST. Experto en extraer la "North Star" del proyecto y crear Blueprints estratégicos. Usa este skill cuando necesites: definir la visión del producto, realizar entrevistas de descubrimiento, crear documentos gemini.md con la lógica del proyecto, o establecer objetivos claros.
Create or update living documentation from git history (branch diff, current branch, PR, or last N commits) for microservices. Use when users ask to document a feature/funcionalidad, document current branch/branch actual, generate release notes/changelog, explain what changed, or update docs for react, integrator, magento, or all services. Produces docs in each repo's docs/ folder (components, changelogs, adrs, runbooks, guides, technical, bugs, plans, tasks) with traceability to commits/files and Obsidian-compatible frontmatter.
Bootstrap AGENTS.md as a short table-of-contents plus a structured docs/ directory (architecture, product specs, acceptance tests, ADRs, exec plans, quality grades). Use when AGENTS.md is missing, when asked to "create AGENTS.md", "bootstrap project for agents", or "set up agent context".
Erstellt und optimiert GraphQL-Queries und Mutations fuer das microtech ERP-System buero+. Deckt den gesamten ERP-Datenbestand ab: Artikel, Warengruppen, Stuecklisten, Adressen mit Anschriften und Ansprechpartnern, Vorgaenge (Angebote, Auftragsbestaetigungen, Lieferscheine, Rechnungen, Gutschriften, Bestellungen), Vorgangspositionen, offene Posten, Lagerbestaende, Projekte, Dokumente (DMS), Kalender, Kontakte, Kontenplan, Zahlungsverkehr und SEPA-Mandate. Unterstuetzt Lesen, Anlegen, Aendern, Loeschen, Buchen (fnPost), Stornieren (fnReverse), Wandeln (fnConvert), Archivieren sowie ERP-Parametertabellen (Vorgangsarten, Steuerschluessel, Zahlungsbedingungen, Einheiten, Versandarten, Waehrungen, Mahnstufen, Adressstatus, Projektstatus, Dokumentenarten, Kommunikationsarten u.v.m.). Verwende diesen Skill wenn der Nutzer mit microtech ERP oder buero+ arbeiten will, ERP-Daten abfragen, Belege erstellen oder verarbeiten will, oder microtech-spezifische Begriffe wie tbl, fld, fnPost, fnConvert, rowRead, rowNew, rowSave, acoGPreis, lnkPostalAddresses, @acquireLocks erwaehnt. NICHT verwenden fuer andere ERP-Systeme (SAP, Shopify, Odoo, Dynamics), allgemeine SQL/Datenbank-Fragen oder generische GraphQL-Schemas ohne microtech-Bezug.
Build a graph-structured dossier on a seed entity via parallel fan-out + recursive expansion across web, memory, knowledge-graph, codebase, ADR index, and git intel
Explains how to use skeeper to keep spec artifacts (SPEC.md, ADRs, RFCs, plan/PRD/TechSpec markdown, custom globs) next to the code they describe without polluting main-repo history. Covers strict hooks, the tracked skeeper.lock file, namespaces, sync/verify/fsck, safe drift workflows with diff/hydrate/reconcile/rescue/update, adopt/untrack/pattern, repair, SKEEPER_SKIP, and the GitHub Action. Use when setting up skeeper, configuring a sidecar, syncing/verifying a lockfile, recovering drift or failed syncs, auditing bypasses, or wiring CI. Do not use for general Git hook questions, repos with no .skeeper.yml and no intent to add one, or editing skeeper internals.