1,072 件 ・ 関連度順
概要と使いどころ
Builds capability — skills gaps, career frameworks, training that transfers to the job, and internal mobility. Use this to design a career ladder, close a capability gap, decide whether to build or hire a skill, structure onboarding into a role, or work out why training keeps failing to change anything.
日本語の概要は準備中です。原文の説明を表示しています。
Builds and interrogates a project schedule — logic-driven sequencing, dependency types and lags, float and the critical path, resource loading and leveling, schedule risk analysis, and measuring progress against a baseline rather than against optimism. Use this to construct a schedule, audit one you have inherited, find out why a plan keeps slipping, work out what a date change actually costs, or judge whether a reported percentage complete means anything.
日本語の概要は準備中です。原文の説明を表示しています。
Assesses and improves how personal data is collected, used, shared, and retained — data mapping, lawful basis, consent, processor agreements, subject rights, and breach obligations. Use this before launching anything that handles personal data, when adding a vendor that will process it, when a data subject request arrives, when assessing exposure under GDPR or US state privacy laws, or when preparing for a privacy review.
日本語の概要は準備中です。原文の説明を表示しています。
Every shot carries its own timecode and shows one visible change on a body. The dread comes from the chain — a look, veins, a bite, the next person — and the ending seals a door without settling anything. Use when the user wants a Seedance 2.5 / 2.0 video prompt for this kind of clip (Horror and suspense; 中文触发词: 恐怖悬疑短片, 恐怖, 悬疑, 惊悚), or asks how published cases of this type were prompted. Read references/cases.md before drafting.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.
日本語の概要は準備中です。原文の説明を表示しています。
Execute via @babysitter. Use this skill when asked to babysit a task, do anything that is structured process-driven (even a loop) or whenever it is called explicitly. (babysit, babysitter, with a process, orchestrate, orchestrate a run, workflow, loop until, etc.)
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs an app on the user's own screen — a native desktop application (instrument control software, Origin, GraphPad, ImageJ, a reference manager, a spreadsheet), or a desktop browser window that needs window-level control. Read before the first `computer` call. Covers the observe-act-observe loop, why element indexes go stale, which action to prefer for which control, what "unverified" means and why it must never be reported as success, and the recovery for each error code. Not for page-level web automation (use the browser connector) and not for anything that can be done from the shell.
日本語の概要は準備中です。原文の説明を表示しています。
House style for user-facing documentation — voice, scope, structure, and what to leave out. Use this skill whenever writing, editing, or reviewing anything a user reads to learn how to use a tool — help center articles, getting-started guides, tutorials, feature docs, README usage sections, in-app help, release notes, or FAQ entries. Trigger it even when the request is phrased plainly — "document this feature", "write docs for X", "explain this to users", "write a README for this library", "turn these notes into a guide" — and even when no style guidelines are mentioned. Also use it to review existing docs for tone, bloat, or leaked implementation detail. Do not use it for internal engineering docs, architecture write-ups, RFCs, or code comments.
日本語の概要は準備中です。原文の説明を表示しています。
Prove that the file you are about to send, publish, or hand off IS the thing you mean — before it leaves your hands. Rebuild from source, check integrity, diff the derived artifact against its source, and require the recipient to echo what they received. Use before sending a paper/PDF for review, shipping a release or replication package, handing files to a coauthor or collaborator, uploading anything to an external reviewer or model, or publishing. Prevents an entire review/QA cycle from being spent on defects that exist only in the artifact, not in the work.
日本語の概要は準備中です。原文の説明を表示しています。
Qualify a check before it is allowed to clear anything — prove it can detect the failure it is meant to catch. Seeds known defects into a copy of a real artifact plus a clean control, runs the checker, and reports recall and false-positive rate into a qualification ledger. Use when the user says "does this check work", "qualify the gate", "test my reviewer", "seed defects", "vaccinate", "qualify the checks", "can I trust this review", "does it pass for the right reason", or before relying on any automated check or referee simulation for a decision that matters. NOT a code fixer and NOT a reviewer itself — it grades the grader.
日本語の概要は準備中です。原文の説明を表示しています。
Triage academic email and calendar (Gmail / Google Calendar via the session's MCP) into a prioritized digest plus a referee-obligations tracker — classifying referee requests, R&R and editor correspondence, co-author threads, seminar and conference invites, and grant/admin deadlines, and proposing a human-gated action for each (draft reply, calendar hold, scaffold a project, snooze). Use when user says "triage my inbox", "check my academic email", "what needs my attention this week", "go through my mail", or when run as a scheduled routine. NEVER auto-sends or auto-accepts anything.
日本語の概要は準備中です。原文の説明を表示しています。
Run Chain-of-Verification (CoVe) on a draft or a block of text with factual claims. Spawns the `claim-verifier` agent in a fresh context (never a conversation fork) so it never sees the draft — then reports which claims are supported, contradicted, or unverifiable. Use when user says "verify these citations", "check the claims in X", "did I hallucinate anything", "fact-check this draft", "run CoVe on this", or after any text generation that asserts facts about papers, datasets, or numerical results. NOT for style/grammar review (use `/proofread`) or substance review (use `/review-paper`).
日本語の概要は準備中です。原文の説明を表示しています。
Before and after changing anything shared — a function's return value, a signature, a schema, a label set, a config default, a constant, a file format — find every consumer and actually run them. Catches the change that looks purely additive but silently breaks a contract in a file you never opened. Use when editing shared code, adding a field/column/return element, renaming, changing units or defaults, or touching a pipeline that produces reported numbers.
日本語の概要は準備中です。原文の説明を表示しています。
Test quality review drawing on twelve classic engineering books — with primary focus on xUnit Test Patterns, The Art of Unit Testing, How Google Tests Software, and Working Effectively with Legacy Code — that diagnoses structural problems in an existing test suite: brittleness, mock abuse, coverage illusions, slow execution, poor readability. Triggers when: user asks about test quality, shares test files for review, or expresses frustration: "tests keep breaking whenever I change anything", "our tests take forever", "tests pass but bugs still reach production", or "we have too many mocks". Do NOT trigger for: writing new tests from scratch (use the regular test-writing workflow) or testing framework/syntax questions — this skill reviews an existing suite for structural quality problems, not individual test authoring.
日本語の概要は準備中です。原文の説明を表示しています。
Run /architect when choosing between approaches, designing a feature or page, picking a tech stack, or when /develop says a decision is owed, anytime a load bearing technical decision is unmade. Asks deep questions, recommends an answer, and writes a build spec to docs/specs/. Owns all spec files.
日本語の概要は準備中です。原文の説明を表示しています。
Diagnoses and safely reclaims macOS disk space: caches, logs, app remnants, large/duplicate files, Docker/OrbStack, Chromium code-sign clones, developer caches. Use when a Mac is low on storage, shows “Caching needs more space”, or before deleting anything to avoid data loss. Not for Windows/Linux or permission issues (use macos-permissions).
日本語の概要は準備中です。原文の説明を表示しています。
Calm a heated conflict — in person or in writing — before it does damage, by lowering the temperature instead of winning the point. Use when asked help me de-escalate this, this argument is getting heated, calm this situation down, or how do I respond without making it worse. Produces a read on what's actually driving the heat (often an unmet need under the surface argument), the de-escalation moves (acknowledge, slow down, find the shared ground), what to say and what to avoid, and how to steer toward resolution once the temperature drops — because you can't solve anything while everyone's activated.
日本語の概要は準備中です。原文の説明を表示しています。
Decode a mainland China labour contract (劳动合同) before signing: probation, pay and its structure, working hours, social insurance, non-compete and confidentiality, termination terms and anything that conflicts with the Labour Contract Law. Use when asked 帮我看看劳动合同, 劳动合同有什么坑, 试用期合法吗, 竞业限制条款, or review my Chinese employment contract. Produces a clause-by-clause decode with red, amber and green flags, the statutory limits each clause must respect, the questions to ask HR, and suggested wording for changes. Not legal advice.
日本語の概要は準備中です。原文の説明を表示しています。
Make a genuinely good drink from the bottles already on your shelf — no special trip, no 12-ingredient recipe. Use when asked what can I make with [spirits], cocktail from what I have, I've got [bottles] what can I drink, or make me a drink without buying anything. Produces two or three cocktails you can build right now with ratios, a method, sensible substitutions for what you're missing, and a zero-proof version — scaled to how many you're making.
日本語の概要は準備中です。原文の説明を表示しています。
Estimate economic compensation (经济补偿金) when employment ends in mainland China: N, N+1 or 2N under the Labour Contract Law, with the high-earner cap, the part-year rule and the questions that decide which case applies. Use when asked 我被裁员了能拿多少补偿, N+1 怎么算, 经济补偿金计算, 违法解除 2N, or how much severance am I owed in China. Produces the scenario that likely applies and why, the calculation shown step by step, what to check before signing anything, and where to get it confirmed. Not legal advice.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Plan an apprentice's or new laborer's first week so they're useful by Friday and safe from hour one — day-by-day teaching order, the safety non-negotiables stated before anything else, what they're allowed to touch unsupervised, and the check-out conversation that decides week two. Use when a tradesperson says 'my apprentice starts Monday', 'how do I train the new guy', or 'the apprentice is useless and I don't have time to teach'. Produces a first-week plan, a can/can't-touch list, and the Friday review script.
日本語の概要は準備中です。原文の説明を表示しています。
Write the band agreement before the money or the breakup arrives — who owns the songs, how money splits (writing vs performing distinguished), who owns the name, what happens when someone quits, and the decision rules for offers — decided while everyone still shares a van. Use when a band asks 'how should we split money', 'who owns our songs', 'our drummer quit, what happens', or is about to record/release/sign anything. Produces a plain-language band agreement and the meeting script to agree it. Not legal advice — it's the conversation that makes the lawyer cheap later.
日本語の概要は準備中です。原文の説明を表示しています。