operator-skills

Use this skill when the user asks to reconcile two or more sources that report different numbers for what should be the same metric, resolve a disagreement between a dashboard and a database query, or debug why two reports do not tie. Trigger phrases include "why do these numbers disagree", "reconcile these reports", "the dashboard does not match the database", "tie out these totals", "reconciliar los números", "por qué no coinciden", "audit these metrics". Produces a reconciliation report that names the root cause and the fix, not just the variance.

Use this skill when the user asks for an adversarial review of a proposal, architecture, system design, agent workflow, or rollout plan. Trigger phrases include "red team this", "adversarial review", "where does this break", "pre-mortem this design", "red team review", "revisión adversarial", "qué puede salir mal", "break my plan". Produces a structured list of failure modes ranked by severity and likelihood, each with a proposed mitigation, not just a list of worries.

Use this skill when the user asks to audit a product's user experience, run a heuristic review, list UX issues, or produce a prioritized backlog of UX tickets. Trigger phrases include "UX audit", "heuristic review", "audit this flow", "review this product", "find UX issues", "auditoría de UX", "revisión heurística". Produces a structured audit ranked by severity and surface area, with each finding translatable into a ticket.

Use this skill when the user asks to write, draft, structure, or revise a record of a decision that has been made. Trigger phrases include "write a decision record", "ADR for X", "document this decision", "registrar la decisión", "ADR", "log this decision", "decision log entry". Produces a record of a bet placed under uncertainty, not a proposal. Works in English and Rioplatense Spanish.

Use this skill when the user asks to write or structure a leadership brief, a board update, or a one-page summary for executives. Trigger phrases include "exec brief", "board update", "one-pager for leadership", "resumen para el board", "brief for the CEO", "summarize this for the board". Produces a single page that leads with the bet, the number, and the ask. Works in English and Rioplatense Spanish.

Use this skill when the user needs to communicate during a live incident. Trigger phrases include "incident update", "status page update", "comms during an incident", "write an incident notice", "draft a resolution note", "all-clear message", "comunicado de incidente", "actualización de estado". Produces calm, factual updates while the incident is still moving. No heroes, no blame. Works in English and Rioplatense Spanish.

Use this skill when the user asks to write, draft, or revise a status update for an external client or stakeholder. Trigger phrases include "client update", "stakeholder update", "delivery status update", "write the update for the client", "update para el cliente", "escalar un retraso al cliente". Produces a client-facing update that reads as a conversation about delivery, not a contract recital. Works in English and Rioplatense Spanish.

Use this skill when the user asks to write or revise a recurring status update for a team or stakeholders. Trigger phrases include "weekly update", "status update", "cycle update", "armemos el update", "update de producto". Reports outcomes, not activity. Scales to a single period or an end-of-cycle wrap. Works in English and Rioplatense Spanish.

Use this skill when the user asks to plan a sprint, set sprint commitments, or work out team capacity for an upcoming iteration. Trigger phrases include "plan the sprint", "sprint planning", "capacity planning", "what can we commit to this sprint", "planificar el sprint", "armar el sprint", "planificación de capacidad". Produces a sprint plan built around one outcome, with commitment and stretch separated. Works in English and Rioplatense Spanish.

Use this skill when the user asks to study a competitor's product surface, flow, or feature by inspecting what they actually shipped. Trigger phrases include "competitive teardown", "competitor analysis", "teardown of X", "análisis de competencia", "tear apart their onboarding", "how does competitor X do Y". Produces a structured teardown grounded in observed behavior, not marketing claims. Works in English and Rioplatense Spanish.

Use this skill when the user asks to turn user research into patterns. Trigger phrases include "synthesize user interviews", "interview notes to patterns", "research synthesis", "what did we learn from these interviews", "cluster these findings", "sintetizar entrevistas". Produces patterns grounded in observed behavior, not a feature list. Separates what users do from what they say. Works in English and Rioplatense Spanish.

Use this skill when the user asks to draft, structure, or revise objectives and key results. Trigger phrases include "draft OKRs", "write objectives and key results", "set goals for the quarter", "armar los OKRs", "OKRs for the team", "turn this into OKRs". Produces objectives as bets with measurable evidence, not a task list. Works in English and Rioplatense Spanish.

Use this skill when the user asks to evaluate a candidate against a rubric, write a structured interview debrief, calibrate an interview panel, or produce a hire or no-hire decision memo. Trigger phrases include "evaluate this candidate", "score this interview", "write the debrief", "hire or no-hire", "evaluar al candidato", "escribir el debrief", "panel debrief", "interview scorecard". Produces a scorecard tied to concrete evidence and a decision memo, with role-specific rubric overrides supported.

Use this skill when the user asks to write a post-mortem, run a retrospective on a shipped or failed project, analyze an incident, or capture lessons from a near-miss. Trigger phrases include "write the post-mortem", "run the retro", "debrief this incident", "what went wrong", "post-mortem de este incidente", "retro del proyecto", "lessons learned", "blameless retro". Produces a timeline of facts, contributing factors, action items with owners, and structural signals, without blaming individuals.

Use this skill when the user asks to evaluate a vendor, score candidate SaaS or services providers, build a vendor scorecard, or decide between two or more commercial options. Trigger phrases include "evaluate this vendor", "compare these tools", "should we buy X or Y", "vendor scorecard", "due diligence on this vendor", "evaluar al proveedor", "comparar estos servicios", "comprar X o Y". Produces a scorecard tied to concrete evidence, a comparison against alternatives, and a decision memo that names post-signing review triggers.

Use this skill when the user asks to specify an internal dashboard, admin tool, back-office UI, operations console, or data-heavy app for a defined audience. Trigger phrases include "spec this dashboard", "admin panel for X", "internal tool", "ops console", "back-office UI", "dashboard de admin", "spec del panel interno". Produces a dashboard spec structured around the question, the user, and the data, with explicit handling of states, roles, and degraded modes.

Use this skill when the user asks to plan a platform-to-platform migration, data migration, system rebuild, or cutover from a legacy product to a new one. Trigger phrases include "migration plan", "cutover plan", "migrate from X to Y", "legacy sunset", "replatforming", "plan de migración", "migrar este sistema", "cutover", "data migration". Produces a migration spec structured around parity, cutover, and rollback, with an inventory-level matrix.

Use this skill when the user asks to scope a custom development engagement, structure a commercial proposal, break work into phases, or decide between time-and-materials and fixed-price. Trigger phrases include "scope this proposal", "price this project", "break this into phases", "T&M vs fixed", "propuesta de alcance", "cotizar este proyecto", "statement of work", "SOW". Produces a scope document structured around phases, deliverables, exclusions, and commercial model.

Use this skill when the user asks to respond to a government, enterprise, or institutional RFP, tender, or vendor questionnaire that requires structured compliance answers. Trigger phrases include "respond to this RFP", "RFP response", "draft the tender", "compliance matrix", "respuesta a licitación", "responder este pliego", "vendor questionnaire", "enterprise deal questionnaire". Produces a compliance-first response structured around the procurement document, not the vendor's pitch.

Use this skill when the user asks to answer a vendor security questionnaire, procurement security assessment, enterprise due diligence form, or privacy impact questionnaire. Trigger phrases include "fill this security questionnaire", "answer this DPA", "security assessment", "vendor due diligence", "responder cuestionario de seguridad", "evaluación de seguridad", "DPIA", "SIG questionnaire", "CAIQ". Produces answers structured around what the company actually does, with explicit gaps and roadmap items, without overclaiming.

Use this skill when the user asks to synthesize a daily or weekly agenda across multiple calendars, orgs, or commitments, or to turn a dumped list of events into a prioritized plan. Trigger phrases include "plan my day", "what does my week look like", "synthesize my agenda", "review my calendar", "armar la agenda", "qué tengo esta semana", "prep for tomorrow". Produces an agenda that flags conflicts, prep needs, and declinable items, not a reformatted calendar export.

Use this skill when the user asks to turn closed tickets, Slack threads, meeting notes, PR descriptions, or email exchanges into durable documentation such as feature docs, runbooks, architecture decision records, or onboarding material. Trigger phrases include "document this feature", "write a runbook from these tickets", "extract docs from this thread", "documentar esto", "pasar a documentación", "write this up". Produces a document structured by surface or topic, not by chronology, with linked primary sources.

Use this skill when the user asks to prepare for a meeting, build a briefing for a one-on-one, anticipate stakeholder reactions, or plan the opening move for a hard conversation. Trigger phrases include "prep me for this meeting", "brief for tomorrow's meeting", "how should I run this conversation", "preparar esta reunión", "brief para la reunión", "what's the plan for this call". Produces a briefing that names the desired outcome, maps stakeholders, anticipates objections, and plans the opening move.

Use this skill when the user asks to triage a backlog of tickets in Linear, Jira, GitHub Issues, Shortcut, or any similar tool, or to decide what a team should do, defer, and decline. Trigger phrases include "triage this backlog", "review my Linear inbox", "what do we pick up next", "clean the backlog", "triage de tickets", "revisar la cola", "decidir qué hacemos". Produces a triage session with a disposition for every ticket, ranked by impact, and a decline message for the ones the team will not do.

Use this skill when the user asks to design product analytics, define events, build an event taxonomy, specify instrumentation for a new feature, or clean up existing tracking. Trigger phrases include "instrument this feature", "define events for X", "event taxonomy", "tracking plan", "analytics spec", "instrumentar esta feature", "taxonomía de eventos". Produces an instrumentation plan structured around the question the data will answer, not around what is easy to fire.

Use this skill when the user asks to pitch a feature, propose a product bet, write a one-pager, or make the case for investing in a piece of product work before committing to a full PRD. Trigger phrases include "pitch a feature", "feature proposal", "make the case for X", "write a one-pager", "propuesta de feature", "proponer un producto", "make the case", "pitch this to leadership". Produces a proposal structured as a bet request, not a spec, with explicit cost to validate and kill criteria.

Use this skill when the user asks to write, draft, structure, or revise a Product Requirements Document. Trigger phrases include "write a PRD", "draft a product spec", "turn this into a PRD", "PRD for X", "escribir un PRD", "spec this feature", "product brief". Produces a PRD as a hypothesis, not a spec. Scales sections to the maturity of the feature. Works in English and Rioplatense Spanish.

Use this skill when the user asks to build a product roadmap grounded in behavioral or business data, reprioritize the backlog based on what the numbers say, or turn a dashboard into a sequenced set of bets. Trigger phrases include "build a roadmap from this data", "reprioritize the backlog", "where should we focus next", "roadmap based on usage", "roadmap a partir de datos", "priorizar con data", "data-driven roadmap", "planning from metrics". Produces a roadmap structured as a sequence of bets, each with impact, uncertainty, cost, and kill criteria.