메뉴
SkillsMP는 koizumikento/stray-plugin에서 57개의 skill을 수집했습니다. skill을 열어 소스와 세부 정보를 확인하세요.
수집된 skill 57개 중 40개를 표시합니다.
Use when the author asks if local Git state is ready to push or an open pull request is ready for initial or repeat human review. Owns a read-only, state-sealed readiness decision. Do not use for general code review, fixes, security preflights, GitHub…
원문 언어: 영어
Use when the user wants working code for an end-to-end web, mobile, or desktop app flow spanning UI and its API, data, auth, or background behavior. Do not use for Slack apps, static corporate sites, landing pages, reviews, test-design-only work, product…
원문 언어: 영어
Use when the user wants an e-Stat 統計表 searched, retrieved, filtered, compared, or analyzed, including a statsDataId. Do not use for KPI ideation or tracing an identified whitepaper chart before its source table is known.
원문 언어: 영어
Use when the user wants MLIT Real Estate Information Library data retrieved, mapped, compared, or analyzed for a defined place/layer. Do not trigger on 地価・不動産 policy discussion without a data operation.
원문 언어: 영어
Use when a durable, source-backed report requires multiple independent research tracks, broad source coverage, conflict resolution, and explicit uncertainty. Do not use for concise web answers, single-track domain briefs, page extraction, or work owned by a…
원문 언어: 영어
Use when one specialized technical, standards, regulatory, market, or academic question needs a focused source-backed brief from authoritative current evidence. Do not use for generic web answers, multi-track deep reports, product decisions, page extraction,…
원문 언어: 영어
Use when current web signals should generate, widen, compare, or tentatively rank idea directions before a final choice is made. Do not use for evidence-free brainstorming, product selection or scope, PRDs, acceptance criteria, validation plans, or finished…
원문 언어: 영어
Use when a named Japanese company, corporate number, or explicit gBizINFO entity lookup needs official corporate-profile or activity data through gbizinfo-mcp. Do not trigger on subsidy, procurement, patent, award, or market topics without a company/entity…
원문 언어: 영어
Use when a Japan weather request needs traceable JMA observations, AMeDAS stations, recent time series, or prefecture forecasts through jma-data-mcp. Do not use for a provenance-free conversational forecast, climate research, non-Japan weather, or emergency…
원문 언어: 영어
Use when a Japanese horse race needs evidence-based contender analysis, probability ranges, value checks, or user-requested ticket candidates from permitted current data. Do not use for profit guarantees, minors, prohibited collection, account operation,…
원문 언어: 영어
Use when current evidence must become a committed product or feature direction with scope, acceptance criteria, and a validation plan. Do not use for option-space exploration, research-only briefs, visual polish, or implementation after product decisions are…
원문 언어: 영어
Use when one general current question or small comparison needs a concise live-web answer and no specialist skill owns it. Do not use for specialized domain briefs, multi-track deep reports, product decisions, terms, patents, news roundups, GitHub triage, or…
원문 언어: 영어
Use when the user wants to create or update a Codex `SKILL.md` in a plugin or repo `.agents/skills/` directory. Do not use for plugin scaffolding, custom subagents, review-only audits, or routing-eval-only work.
원문 언어: 영어
Use when the user wants to design, run, or repair trigger and near-miss routing cases for Codex skills. Do not use for authoring the skill itself, general software tests, or AI eval CI implementation.
원문 언어: 영어
Use when the user wants to create or update a reusable Codex custom subagent in project `.codex/agents/` or explicitly requested personal `~/.codex/agents/`. Do not use for skills, one-off delegation prompts, or conceptual multi-agent design only.
원문 언어: 영어
Use when the user wants to draft or substantially revise a publishable article, blog post, or newsletter from a brief or supplied sources, including angle, structure, prose, and source treatment. Do not use for research-only briefs, short marketing copy, or…
원문 언어: 영어
Use when the user wants to plan, create, repair, or package pixel-art sprites, tiles, icons, item sheets, mascots, or short loops. Do not use for Codex pet atlases, generic image editing, vector/logo design, game implementation, screenshots, or brand systems.
원문 언어: 영어
Use when a defined feature for iOS, iPadOS, macOS, watchOS, tvOS, or visionOS needs an implementation-ready UI spec grounded in user-authored notes from official Apple design pages, with source URLs and access dates. Do not use for strategy, UI audits,…
원문 언어: 영어
Use when the user wants a findings-first review of code, docs, UI, skills, plugins, prompts, evals, or releases, including an explicitly requested bounded review-fix loop. Do not use for push or PR review-request readiness, blank-slate creation, security-only…
원문 언어: 영어
Use when the user wants a review-only security preflight of a repository, diff, app/API, CI/CD, release, dependencies, IaC, containers, or secret/data handling. Do not use for fixes, broad code review, active probing, incident response, penetration testing,…
원문 언어: 영어
Use when the user wants to plan, build, debug, validate, install, deploy, or automate a Slack app using Slack CLI, manifests, Bolt, Deno SDK, events, commands, workflows, or Web API calls. Do not use for generic apps, terms/compliance research, message…
원문 언어: 영어
Use when the user wants Japanese official documents 一時保存・索引・cache inspected, repaired, or traced under tmp/japan-govdocs/. Do not use for ordinary reading unless local storage or provenance is central.
원문 언어: 영어
Use when an MCP server needs protocol-aware design or review: tools/resources/prompts, transport, auth, pagination, errors, and client boundaries. Do not use for generic API design, skill authoring, or implementation-only coding with an already settled MCP…
원문 언어: 영어
Use when the user wants to build, debug, test, simulate, containerize, or CI-enable a ROS 2 workspace or application integration. Do not use for ROS 1, pure CAD/circuits, deep specialist stacks, firmware, or unapproved live-hardware operation.
원문 언어: 영어
Use when the user wants repeatable AI or agent evaluations enforced in CI, including model comparisons that must become a quality gate. Do not use for ordinary tests, one-off prompt checks, or skill-routing cases without CI.
원문 언어: 영어
Use when the user wants to create or revise a static, repository-managed corporate site with durable company and trust pages plus responsive implementation. Do not use for CMS/editorial workflows, single-offer landing pages, data-backed product flows, brand…
원문 언어: 영어
Use when the user wants a neutral 課題背景・社会背景 or government framing built from Japanese official sources. Do not use for proposal-ready advocacy, a specific claim's evidence, or a named-document summary.
원문 언어: 영어
Use when the user wants to trace a Japanese policy theme to 予算, government programs, or 行政事業レビュー and distinguish funding lifecycle states. Do not use for eligibility, application, or procurement advice.
원문 언어: 영어
Use when the user wants official 自治体事例・企業事例 or precedent initiatives for a Japanese policy issue, with evidence quality and transfer limits. Do not use for general evidence, KPI discovery, or causal-effect claims.
원문 언어: 영어
Use when the user identifies a specific Japanese government chart, table, figure, source note, or statistic and wants its 元データ or reproducibility traced. Do not use to brainstorm KPIs or generally search e-Stat.
원문 언어: 영어
Use when the user supplies existing Japanese government 引用・URL and wants officiality, freshness, 最新版, edition, or claim-fit audited. Do not use to find evidence from scratch unless the audit exposes a specific gap.
원문 언어: 영어
Use when the user provides a claim and wants official Japanese government 根拠・出典 to support, qualify, or reject it. Do not use for neutral background, KPI discovery, citation freshness audits, or broad document summaries.
원문 언어: 영어
Use when the user asks what official 指標 or KPI candidates could measure a Japanese social issue or intervention. Do not use to trace a specific chart or to retrieve/analyze a chosen e-Stat table.
원문 언어: 영어
Use when the user asks which Japanese 省庁・所管 or policy context formally owns or materially shares a theme. Do not use for budget tracing, priority scoring, or a single-document summary.
원문 언어: 영어
Use when the user asks whether a theme is a current/rising 政策優先度 or 国が重視する課題 and wants official signals compared over time. Do not use for generic evidence, formal ownership, or future-funding predictions.
원문 언어: 영어
Use when the user wants 国交省Project LINKS・G空間 datasets cataloged, retrieved, profiled, joined, or analyzed. Do not use for generic policy research, live transport feeds, or non-LINKS geospatial data.
원문 언어: 영어
Use when the user wants a product, service, or initiative synthesized into 官公庁向け提案・企画書 context. Do not use for neutral background, a direct document summary, or procurement/legal advice.
원문 언어: 영어
Use only when a 政府資料・白書 request is broad, mixed, or ambiguous and its primary action is unclear. Classify by requested action, then apply the specialized skill in the same task; do not stop at routing.
원문 언어: 영어
Use only when a specific Japanese 白書・年次報告・章 is the primary object to read or 要約. Do not use when proposal wording or cross-source policy synthesis is the main deliverable.
원문 언어: 영어
Use when a team needs a current official-source check of API or SaaS usage terms for a defined service, account plan, contracting entity, region, and intended use. Do not use for legal opinions, OSS license review, vendor selection, or repository-wide release…
원문 언어: 영어