4,856 件 ・ 関連度順
概要と使いどころ
Guided, conversational walkthrough that explains code, UI, UX, features, or .copilot-tracking artifacts with navigable evidence links, a deep review before explaining, and a reconciled decisions-and-changes ledger. Use when the user wants to understand how something works or why it was changed.
日本語の概要は準備中です。原文の説明を表示しています。
Microsoft Cloud Security Benchmark (MCSB v2) control-domain taxonomy and NIST 800-53 / CIS Controls crosswalk for planning and reviewing Azure cloud resources.
日本語の概要は準備中です。原文の説明を表示しています。
Decision-driven HVE-Core installer with multiple clone-based and extension install methods, environment detection, and selective component installation
日本語の概要は準備中です。原文の説明を表示しています。
Authoring skill for Architecture Decision Records (ADRs) supporting capture, from-planner-handoff, and adopt-template entry modes with selectable Y-Statement or MADR v4.0.0 output templates, supersession lineage, and ASR trigger evaluation.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when picking or diagnosing a training move (SFT, LoRA, DPO/KTO/ORPO, RFT, GRPO/PPO/RLOO, RLHF), or when the user mentions fine-tuning, post-training, training recipe, reward design, or weight updates. Decision tree by reward shape, smoke-run gate, three failure diagnostics, five false-progress patterns. Provider recipes and I/O contract in references/.
日本語の概要は準備中です。原文の説明を表示しています。
Designs and audits macOS launchd watchdogs. Use for LaunchAgent/LaunchDaemon setup, plist changes, scheduled self-healing, repeated notifications, apps reopening after quit, crash or repair loops hammering the Mac, or a watchdog alert shown as Script Editor. Covers stop/disable/restart, cooldown/backoff, notification throttling and alert decisions. 中文：launchd 守护进程、常驻任务、开机自启、后台监控、定时自愈、通知来源排查。
日本語の概要は準備中です。原文の説明を表示しています。
Only for explicit prior-work/reuse/history requests, not status checks. Finds and verifies existing work before new production when reuse is plausible. Use when the user explicitly references earlier work, existing code, history, or prior decisions, or says 以前做过, 已有代码, 别重复造轮子. Not for current tests, files, bug fixes, or mechanical verification. Produces a reuse/adapt/reject receipt; zero hits never prove absence.
日本語の概要は準備中です。原文の説明を表示しています。
Transforms vague prompts or feature requests into precise, testable specifications using EARS (Easy Approach to Requirements Syntax) grounded in relevant domain theories (GTD, BJ Fogg, Gestalt). Use when requirements lack triggers or measurable outcomes, or the user asks to "optimize my prompt" / "improve this requirement" / "make this more specific".
日本語の概要は準備中です。原文の説明を表示しています。
Set up and send technical status notifications through WeCom (Enterprise WeChat) webhooks. Use this skill whenever the user needs to send notifications, alerts, backup completion reports, or status updates via WeCom; when they mention 企业微信, 企微机器人, webhook, or alerting; or when a message needs to be clear, unambiguous, and technically precise rather than vague or condescending.
日本語の概要は準備中です。原文の説明を表示しています。
Write a credit memo for a lending decision: borrower story, facility structure, repayment sources, financial-ratio spread with covenant headroom, risk factors with mitigants, risk-rating rationale, and a recommendation. Use when asked to write a credit memo, credit application, credit paper, loan write-up, or prepare a deal for credit committee. Produces a complete credit memo ready for committee review.
日本語の概要は準備中です。原文の説明を表示しています。
Reconcile controlled-substance records and prepare for an inspection — the count against the register, the discrepancy investigation, the documentation an inspector asks for, and the reporting obligations a shortfall triggers. Use when asked to reconcile controlled drugs, prepare for a DEA or controlled-drug inspection, investigate a discrepancy or suspected diversion, or audit the CD register. Produces the reconciliation, the discrepancy investigation record, the inspection-readiness checklist, and the escalation and reporting decision tree. A process framework only; reporting thresholds, timelines and obligations are set by law in your jurisdiction and must be verified there.
日本語の概要は準備中です。原文の説明を表示しています。
Stress-test a decision or claim through a sharp, fair Q&A — the questions a good lawyer or skeptical friend would ask before you commit. Use when asked to cross-examine me, ask me hard questions about this, interrogate my plan, or make me defend this. Produces a sequenced line of probing questions (from clarifying to challenging to the killer question), space to answer, and a debrief on where your answers were strong, evasive, or exposed a gap — so weaknesses surface in private before they surface in public.
日本語の概要は準備中です。原文の説明を表示しています。
Compress tool outputs, logs, and JSON before they enter the context window — structural compression via a deterministic stdlib script (schema + samples + stats instead of 300 raw rows), no API, no summarization loss. Use when asked shrink this tool output, my context is full of JSON, compress these logs before analysis, or stop wasting tokens on raw data. Produces the crushed artifact with its token math shown, the crush-or-keep decision rules, and the fetch-the-original escape hatch.
日本語の概要は準備中です。原文の説明を表示しています。
Write calm, businesslike co-parenting messages that keep the focus on the kids and stay out of the old conflict — for scheduling, expenses, decisions, and hard topics. Use when asked to write a message to my co-parent, respond to my ex about the kids, co-parenting communication help, or how to reply without a fight. Produces a message drafted in a neutral, child-centered tone (the 'BIFF'-style brief/informative/friendly/firm approach), the bait removed, a clear ask or answer, and a note on documentation — steering away from anything that escalates. Not legal advice.
日本語の概要は準備中です。原文の説明を表示しています。
Start a cross-team project with the collaboration contract that prevents the classic collisions — who decides what, how work flows between teams, the communication channels and cadence, and what done means — agreed before the first collision instead of during it. Use when asked kick off this cross-team project right, our two teams keep colliding, define how we'll work with the other team, or set up the partnership before we start. Produces the one-page contract: decision rights, interfaces, cadence, and the done-definition.
日本語の概要は準備中です。原文の説明を表示しています。
Compare childcare options — nursery/daycare, childminder, nanny, family, or a mix — for your family's real needs, budget, and values. Use when asked to compare childcare options, nursery vs nanny, how to choose childcare, or find the right childcare. Produces a needs-and-values profile, a side-by-side of the realistic options on cost/flexibility/socialization/control, the questions to ask and red flags to check on visits, a total-cost read (including subsidies), and a decision that fits your priorities — not a generic ranking.
日本語の概要は準備中です。原文の説明を表示しています。
Run a consulting client discovery session — uncover the real problem, scope, and decision process. Use when asked to prepare for a client discovery call, qualify a consulting lead, scope an engagement, or run a kickoff. Produces a discovery plan — the questions that surface the real problem (not the stated one), budget/authority/timeline qualifiers, success criteria, red flags, and a follow-up that leads to a proposal.
日本語の概要は準備中です。原文の説明を表示しています。
Send your position to a meeting instead of your body — a one-page brief carrying your stances, fallbacks, red lines, tradables, and delegation limits, readable by the colleague (or agent) representing you. Use when you can't attend a decision-making meeting, when double-booked, when briefing someone to negotiate for you, or 'what would you need from me to represent me?'. Produces the clone brief plus a 60-second verbal version for the person carrying it.
日本語の概要は準備中です。原文の説明を表示しています。
Turn a folder of accumulated documents into one decision-ready brief — the skim-map pass over the pile, the extraction against the brief's actual questions, the conflict reconciliation when documents disagree, and the provenance trail back to sources. Use when asked read all this and tell me what matters, synthesize this folder for the new lead, turn these 20 docs into a brief, or what does all this material actually say. Produces the pile map, the question-driven extraction, the reconciled brief with per-claim sources, and the didn't-read honesty ledger.
日本語の概要は準備中です。原文の説明を表示しています。
Run the pre-flight checklist before an agent drives a browser — the untrusted-web-content threat (every page is attacker-controllable), the credential and session-cookie exposure, the action-confirmation gates for purchases and posts, and the sandboxing that limits the damage. Use when asked let my agent browse safely, is it safe to give the agent computer/browser use, guardrails before the agent uses my browser, or review my browser agent's setup. Produces the sandbox decision, the content-injection defenses, the action gates, and the credential-isolation rules.
日本語の概要は準備中です。原文の説明を表示しています。
Interview you into a durable personal MEMORY.md — your decision rules, patterns, past failures, and preferences — that any AI can read to help you better, with privacy guardrails built in. Use when asked to build my memory file, help my AI remember me, create a MEMORY.md, or set up context about myself. Produces a structured personal-context file drawn out through good questions (how you decide, what you keep repeating, what you don't want to repeat), organized for an AI to use — while explicitly refusing to store sensitive data like credentials, financial, health, or others' personal info.
日本語の概要は準備中です。原文の説明を表示しています。
Turn interview notes into a structured candidate scorecard and hire recommendation. Use when asked to write an interview scorecard, a candidate evaluation, an interview debrief, or to summarize feedback into a hire/no-hire call. Produces a per-competency assessment with evidence and ratings, an overall recommendation with confidence, and the open questions for the next round — evidence-based, bias-aware, and decision-ready.
日本語の概要は準備中です。原文の説明を表示しています。
Write a clear, reproducible bug report that gets fixed fast. Use when asked to write a bug report, file a defect, report an issue, or turn 'it's broken' into an actionable ticket. Produces a structured report — a precise title, steps to reproduce, expected vs. actual, environment, severity/priority, and evidence — so a developer can reproduce and fix it without a back-and-forth.
日本語の概要は準備中です。原文の説明を表示しています。
Think clearly about whether bankruptcy is the right move, or whether another path fits better — without shame and without a sales pitch. Use when asked should I file for bankruptcy, is bankruptcy my best option, alternatives to bankruptcy, or what happens if I file. Produces an honest read on whether your situation is the kind bankruptcy actually helps, the main types and what each does (and doesn't) discharge, the real trade-offs (what you keep, the credit impact and its recovery, what's not dischargeable), the alternatives to weigh first (negotiation, debt management, doing nothing on time-barred debt), and a strong push to consult a bankruptcy attorney. Not legal advice.
日本語の概要は準備中です。原文の説明を表示しています。