「ada」の検索結果

Resolución estructurada de problemas en 6 pasos: Definición del problema, objetivos, lluvia de ideas, evaluación, implementación y revisión.

日本語の概要は準備中です。原文の説明を表示しています。

Canalización automatizada de desarrollo de software. Escanea proyectos, prioriza tareas, analiza código u orquesta bucles de desarrollo. Cero dependencias (solo la biblioteca estándar de Python).

日本語の概要は準備中です。原文の説明を表示しています。

Protocolo para crear, publicar, lanzar, auditar y mantener repositorios de GitHub de forma segura: verificar reglas locales y bloqueos, crear .gitignore antes del primer git add, realizar verificaciones de privacidad, preparar README/i18n/banner/metadatos, verificar etiquetas de release y lanzamientos de GitHub, y actualizar perfiles de organización, archivos llms.txt y enlaces a registros.

日本語の概要は準備中です。原文の説明を表示しています。

Orquestación multimodelo y estrategia de cambio de modelos. Selección de modelos basada en puntuación, delegación entre agentes (Gemini, Codex, Ollama), emparejamiento con advisor, disparadores de escalado, matriz de permisos y optimización de eficiencia de costos.

日本語の概要は準備中です。原文の説明を表示しています。

Activación conductual para la depresión: romper el círculo vicioso, registro de actividades, planificación semanal y actividades basadas en valores.

日本語の概要は準備中です。原文の説明を表示しています。

Protocolo sistemático de depuración en 6 fases. Enfoque estructurado ante errores con verificaciones rápidas, pruebas aisladas, regla de los 20 minutos y plantilla de informe de errores.

日本語の概要は準備中です。原文の説明を表示しています。

Calendar skill with user-adaptive backend selection (Flag 3). Default: local SQLite store. Optional: Google Calendar MCP, Routinika or UpToday as backend — controlled via assist/prefs.json. Without preference the LLM asks the user interactively.

日本語の概要は準備中です。原文の説明を表示しています。

Protocol for safely creating, publishing, releasing, auditing, and maintaining GitHub repositories: check local rules and locks, create .gitignore before the first add, run privacy checks, prepare README/i18n/banner/metadata, verify release tags and GitHub releases, and update organization profiles, llms.txt files, and registry links.

日本語の概要は準備中です。原文の説明を表示しています。

Drafts answers to the questions in a received RFP, RFQ or tender from the organisation's past responses, answer library, case studies, policies and other documents provided: one row per buyer question with a draft answer marked Reused, Adapted or Missing, its source and date, and a legal or pricing review flag on every answer touching terms, liability, warranties, insurance, data protection or price. Use when the user asks to "draft our RFP response", "answer this tender from our past proposals", "pre-fill the bid questions", "first pass at the RFQ answers" or "reuse our previous bid content". Do not use for writing the buyer's own RFP or requirements, use rfp-requirements-pack instead; for security or due diligence questionnaires use vendor-security-questionnaire-prefill; for scoring received supplier responses use rfp-comparison-pack. Drafts for human review; never approves, authorises or signs off.

日本語の概要は準備中です。原文の説明を表示しています。

Pre-fills a customer's or prospect's security or third-party risk questionnaire from the organisation's own answer sources (prior questionnaires, answer library, policies), returning one row per question with a draft answer marked Reused, Adapted, Missing or Routed, its source, date, scope match and owner, plus the Missing list by owner. Never invents an answer, certification or control and never submits. Use when the user asks to "pre-fill this security questionnaire", "take a first pass at the customer's due diligence form", "answer this vendor assessment from our previous responses", "populate the third-party risk questionnaire" or "which questions can we reuse answers for". Do not use for screening a vendor's own answers, use vendor-risk-screening-brief instead; for RFP or tender answers use rfp-response-drafter. Drafts for human review; never approves, authorises or signs off.

日本語の概要は準備中です。原文の説明を表示しています。

Turns one meeting transcript, recording recap or set of raw notes into concise DRAFT minutes returned in the chat as a single Markdown document: header metadata, attendance and apologies, agenda items each with a short neutral summary and outcome, numbered decisions with an owner, numbered action items with owner and due date, open questions, carried-over actions and the next-meeting line, every entry backed by a short verbatim source fragment and every missing fact marked UNKNOWN. Use when the user asks to "write the minutes", "draft minutes from this transcript", "turn these notes into meeting minutes", "produce the minutes of meeting for today's call", "tidy my rough minutes into the standard format" or "prepare the minutes for circulation". Do not use for extracting action items, task lists or per-owner follow-up emails alone, use transcript-to-actions instead. Drafts for human review; never approves, authorises or signs off.

日本語の概要は準備中です。原文の説明を表示しています。

Drafts one knowledge article or known-error article from a resolved incident or ticket thread: symptoms as reported, environment, cause exactly as the resolver stated it, resolution steps as performed, workaround with its limits, verification, things tried without effect, related records, keywords and proposed metadata, every statement traced to a ticket note or marked UNKNOWN, with a redaction log and a question list for the knowledge owner. Never decides a root cause, adds a step or publishes. Use when the user asks to "write a KB article from this ticket", "turn this resolved incident into a knowledge article", "draft a known error record for this", "document the fix we just did" or "make this thread into a how-to for the service desk". Do not use for a procedure the team will execute (runbook, operating procedure, playbook), use runbook-drafter instead; for a post-incident review, use incident-postmortem-drafter. Drafts for human review; never approves, authorises or signs off.

日本語の概要は準備中です。原文の説明を表示しています。

Sweeps a SharePoint library listing (an export or a listing the agent can reach, with file name, link, review-date column and owner column) for documents past their review date and returns a dated DRAFT review sweep report (Overdue, Due soon, No review date, Summary) plus one ready-to-paste reminder per document owner for the user to send. Never changes metadata, sends a message or invents a document, date or owner. Use when the user asks to "find the documents past their review date", "run the review sweep on the policies library", "which documents are overdue for review", "audit the review dates in this library export" or "draft reminders to owners about stale documents". Do not use for duplicate, conflict and ownership checks across knowledge files, use knowledge-base-hygiene-review instead; for gaps in an engineering deliverables register, use master-document-register-check. Drafts for human review; never approves, authorises or signs off.

日本語の概要は準備中です。原文の説明を表示しています。

Author Mermaid diagrams that parse the first time: choose the right diagram type for the question, write syntax the parser accepts, and keep the picture readable in a narrow panel. A bundled reference covers complex, large diagrams.

日本語の概要は準備中です。原文の説明を表示しています。

Organize user-scoped CLEC episodes into traceable Traditional Chinese Obsidian pages. Use when Codex must group X, pCloud, Google Drive, Bilibili, Odysee, and RSS or Podcast sources by five-digit episode number; obtain and review transcripts through media-transcript; clean readable transcripts with the confirmed CLEC lexicon; anonymize students; or build the standard three-layer episode page.

日本語の概要は準備中です。原文の説明を表示しています。

Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use when asked to "simplify code", "clean up code", "refactor for clarity", "improve readability", or review recently modified code for elegance. Focuses on project-specific best practices.

日本語の概要は準備中です。原文の説明を表示しています。

Convert a BMad skill into a downloadable web bundle (Gemini Gem + ChatGPT Custom GPT) with a persona, install instructions, and knowledge files. Use when a user wants to publish a skill to consumer LLM platforms (Gemini, ChatGPT).

日本語の概要は準備中です。原文の説明を表示しています。

Query Sentry issues, events, releases, replays, and org/project metadata via REST API. Use when the user wants to diagnose a production error, pull stack traces, list recent issues, inspect a release, or fetch event data programmatically — prefer this over asking for UI screenshots or guessing from memory.

日本語の概要は準備中です。原文の説明を表示しています。

- Track aircraft and vessels from public ADS-B and AIS broadcasts using ADS-B Exchange, Flightradar24, FlightAware,… Use when following a tail number or flight, looking up an ICAO 24-bit hex code, registration or callsign, tracing a ship by IMO number or MMSI, checking a flag of convenience or port-call history, finding who owns a private jet or vessel

日本語の概要は準備中です。原文の説明を表示しています。

- End-to-end workflow to establish where and when a photo or video was captured and whether it is authentic — evidentiary handling, metadata extraction, reverse image search for provenance, visual geolocation, chronolocation from shadows, and manipulation… Use when asked to verify where an image was taken, confirm or refute a claimed location or date, or authenticate media before relying on it

日本語の概要は準備中です。原文の説明を表示しています。

- Deep-dive a subject's social media presence — profile metadata, follower and mutual network, content analysis, and posting-time pattern of life across Instagram, Facebook, X/Twitter, TikTok, LinkedIn, Reddit, Telegram and… Use when profiling a social account, mapping someone's associates, inferring a subject's timezone or routine from their posts, or archiving a profile before it is deleted

日本語の概要は準備中です。原文の説明を表示しています。

Keep serialized build-in-public content continuous: read one canon file of season, arcs, beats and loops and say which narrative beat to advance next, so episodes chain into a series. Pairs with the episode adapter, which does the writing. Triggers: "/reality-show", "season state", "what arcs are open".

日本語の概要は準備中です。原文の説明を表示しています。

Deployless delivery-model audit. Use first when adapting any repository toward single-mainline development, automatic deployment from main, runtime release controls, production-trace-driven iteration, AI PR governance, or multi-agent delivery workflows.

日本語の概要は準備中です。原文の説明を表示しています。

Bring an EPA SWMM (.inp) or EPANET (.inp) model into MIKE+ via the mike-plus MCP server — the bridge from an INP builder such as SWMMCanada or agentic-swmm into a MIKE+ database that mike_model_info / mike_run can use. Use when the user has an .inp and wants it in MIKE+. Requires MIKE+ installed + a checked-out license (demo mode caps the model size).

日本語の概要は準備中です。原文の説明を表示しています。