Explorar skills
69.576 skills encontradas
document-quality-standards
Use when creating or editing documents (DOCX, PDF, XLSX, PPTX) that need professional output. Adds visual verification, typography hygiene, and formula patterns.
agentmako
TRIGGER when: user is working in an unfamiliar repo, asks 'where is X', 'what touches Y', needs broad search across code/schema/routes, or is unsure which mako tool fits the task. Covers `reef_ask`, `reef_status`, `reef_verify`, `reef_impact`, `mako_help`, `tool_search`, `context_packet`, `live_text_search`, `lint_files`, and `tool_batch`.
docx-advanced-patterns
Advanced python-docx patterns for nested tables, complex cells, and content extraction beyond .text property. Techniques for forms, checklists, and complex layouts.
agentmako
TRIGGER when: user wants an investigation packet, pre-ship artifact, recall of prior work or answers, or to log tool-run feedback / inspect telemetry. Covers `suggest`, `investigate`, `workflow_packet`, `tenant_leak_audit`, `health_trend`, `issues_next`, `session_handoff`, all four artifact tools, `recall_answers`, `recall_tool_runs`, `agent_feedback`, `agent_feedback_report`, `runtime_telemetry_r
spec-writer
Generate structured software specifications for features, bug fixes, and products. Use when the user wants to create a spec, PRD, feature brief, requirements document, or when starting any new implementation that needs a specification first. Invoke via /spec-writer or when the user says "write a spec", "spec this out", "create a spec", "I need a spec for...", or describes a feature they want to bu
agentmako
TRIGGER when: user wants entity-wide context for a table, route, or RPC -- schema + RLS + readers + writers + downstream touches all at once. Covers `table_neighborhood`, `route_context`, `rpc_neighborhood`.
agentmako
Start here when working in a project with the mako-ai MCP server configured. Entry point that explains how mako's tool skills are organized and carries the policy for logging `agent_feedback` vs acknowledging static findings with `finding_ack`.
project-retrospective
Use when a project needs multi-session retrospective analysis: after milestones, before starting a new phase, when vision drift is suspected, or every 3-5 sessions. Triggers include user saying retro, run a retro, since-last-retro; asks to analyze patterns, recurring mistakes, or correction trends across multiple sessions; says how did we get here or project history in a project-arc context (not s
rtl-document-translation
Translate structured documents (DOCX) to RTL languages (Arabic, Hebrew, Urdu) while preserving exact formatting, table structures, colors, and layouts. Handles quote normalization, multi-pass translation matching, and RTL-specific formatting patterns.
agentmako
TRIGGER when: user wants an investigation packet, pre-ship artifact, recall of prior work or answers, or to log tool-run feedback / inspect telemetry. Covers `suggest`, `investigate`, `workflow_packet`, `tenant_leak_audit`, `health_trend`, `issues_next`, `session_handoff`, all four artifact tools, `recall_answers`, `recall_tool_runs`, `agent_feedback`, `agent_feedback_report`, `runtime_telemetry_r
agentmako
Start here when working in a project with the mako-ai MCP server configured. Entry point that explains how mako's tool skills are organized and carries the policy for logging `agent_feedback` vs acknowledging static findings with `finding_ack`.
agentmako
TRIGGER when: user is working in an unfamiliar repo, asks 'where is X', 'what touches Y', needs broad search across code/schema/routes, or is unsure which mako tool fits the task. Covers `reef_ask`, `reef_status`, `reef_verify`, `reef_impact`, `mako_help`, `tool_search`, `context_packet`, `live_text_search`, `lint_files`, and `tool_batch`.