「fts」の検索結果

Drafts one internal or external announcement (email, intranet post, town hall script, customer notice or press statement) in the organisation's voice from the facts, audience, sender and style guide the user provides, with a fact trace, reader-questions check, pre-send checks and an approvals checklist left blank for the named approvers. Use when the user asks to "announce this change to all staff", "draft the customer notice", "write the town hall script", "prepare a holding statement" or "rewrite this in our voice". Do not use for a digest of several items, use internal-newsletter-drafter instead; to pre-test a drafted message against personas, use communication-pretest-panel. Drafts for human review; never approves, authorises or signs off.

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

Compares a changed HR policy with the version it replaces and drafts a clause-by-clause change log, a plain-language DRAFT employee briefing, a manager FAQ answered only from the policy text with clause references, and a list of open questions the people team must settle before release. Use when the user asks to explain, announce, summarise or brief a policy change, a new policy version or an updated handbook section, or says "what changed in the leave policy", "brief managers on the new handbook section" or "compare the old and new versions of this policy". Do not use for a single announcement with no version comparison, use announcement-drafter instead; for an FAQ from documents that are not a policy change, use faq-builder; for contract clauses, use clause-comparison-table. Drafts for human review; never approves, authorises or signs off.

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

Prepares the contents of a dated backup of a custom skills folder and drafts a session journal entry, both for the user to save, so work can be resumed after a crash, a context loss or a skills wipe. Returns the copy action list, backup manifest, journal entry, resume summary and a restore plan whose steps the user confirms one by one and carries out. Use when the user asks to "back up my skills folder", "checkpoint this session", "write the session journal", "where did we leave off last time", "restore my skills from the last backup" or "take a safety copy before I edit this skill". Do not use for holding individual file changes for approval during ordinary work, use no-delete-guardrail instead. Drafts for human review; never approves, authorises or signs off.

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

Drafts a DRAFT job description from a role brief, team context and the organisation's own template, in inclusive plain language, with every requirement traced to its source, unconfirmed fields marked TBC and a numbered list of items the hiring manager must confirm before posting. Use when the user asks to "write a job description", "draft the job ad", "refresh this role profile", "tidy up this vacancy notice" or "turn these notes into a job posting" from a brief, notes or an old job description. Do not use for interview questions or a scorecard from the finished job description, use interview-scorecard-builder instead; for the new hire's first 90 days, use onboarding-plan-builder. Drafts for human review; never approves, authorises or signs off.

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

Turns an actuals-versus-budget extract (spreadsheet, export or pasted table) into a DRAFT variance table with absolute and percentage variances, favourable or adverse marking and a ranking by size, then drafts plain-language driver hypotheses for each material variance as questions to verify with a named owner, never as asserted causes. Use when the user asks to "explain these variances", "why are we over budget on this line", "write the variance commentary for the management pack", "actuals versus budget analysis" or "which lines drive the variance". Do not use for a dataset with no budget or comparison column, use dataset-insight-pack instead; for weekly operational figures against last week, use kpi-weekly-report-writer. Drafts for human review; never approves, authorises or signs off.

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

Drafts a document transmittal (header, one line per document with revision and purpose of issue, distribution with action required, blank acknowledgement block) from a document list and the project's transmittal template, with UNKNOWN for anything not stated and questions for document control. Never assigns a transmittal number, changes a revision or marks anything issued. Use when the user asks to "draft a transmittal for these documents", "fill in the issue sheet" or "prepare the document issue note". Do not use for checking a register or deliverables list, use master-document-register-check instead. Drafts for human review; never approves, authorises or signs off.

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

Reads one spreadsheet, CSV export or pasted table together with the user's question and drafts an insight pack: a data profile, observations cited to named columns and values and framed as leads, caveats, and suggested charts and follow-up analyses. Every figure carries the label "as read, verify in source"; correlation is never stated as causation. Use when the user asks to "profile this spreadsheet", "what does this data say", "find anomalies in this extract", "give me a first read on this CSV" or "summarise this table". Do not use for a purchase order log or spend extract, use purchase-order-anomaly-review instead; for actuals versus budget, use budget-variance-explainer instead; for a report that arrives by email on a schedule, use report-attachment-analyzer instead. Drafts for human review; never approves, authorises or signs off.

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

Drafts an architecture or design decision record (ADR) from the discussion notes, design review minutes, chat threads and diagram descriptions the user provides: context, decision drivers, options considered with arguments as stated, the decision as the group worded it, consequences and a review date, with every factual claim tagged evidenced, asserted or UNKNOWN so unsupported claims are marked for the author to substantiate. Use when the user asks to "write an ADR", "document the architecture decision", "record why we chose this design", "turn these design review notes into a decision record" or "draft the design decision log entry". Do not use for a business or governance decision with no technical design, use decision-memo-builder instead; for the change ticket that implements the decision, use change-request-pack. Drafts for human review; never approves, authorises or signs off.

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

Draft short, in-voice reply candidates to a fresh community shortlist: read the nightly detector report, pick posts in safe or opinion topics, pull a grounding snippet from the local corpus, and write the drafts. Drafts only, and the owner posts. Triggers: "/sostav-comments", "draft replies to the shortlist".

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

Brand-narrative single source of truth (Busabase App-in-Skill) built on the TALE discipline — Trace / Architect / Land / Evaluate. The agent drafts positioning, the message house of value pillars, the story bank, evidence-backed proof points, and vocabulary/tone guardrails; the human curates which drafts become the CANONICAL narrative; a drift monitor flags off-brand usage across channels. Use when the user invokes $kelly-brand or /kelly-brand, mentions brand narrative, brand messaging, positioning, message house, value pillars, story bank, proof points, tone/vocabulary guardrails, narrative quality (NQS), brand drift, or wants a single source of truth for what the brand says.

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

Write or edit Japanese articles, reports, guides, and public-facing drafts so the argument is clear and the prose reads naturally. Preserve the author's meaning, evidence, and voice when revising. Use for requests to write from a topic or notes, remove AI臭 / AIっぽさ, improve awkward wording or structure, or format notes as 箇条書き, チーム共有, 社内共有, a decision note, handoff, Slack post, or Teams post. For existing prose, ask Gemini through Antigravity CLI to rewrite naturally by default, then audit against the source; use the current model if unavailable. Do NOT use for ordinary Japanese answers, progress updates, technical explanations, code review, English-only prose that is not a bullet-formatting request, or an explicitly incompatible format.

Normalizes ChIP-seq data using exogenous spike-in (ChIP-Rx with Drosophila chromatin per Orlando 2014 / Egan 2016; E. coli carryover for CUT&RUN/CUT&Tag). Distinguishes RRPM from Rx-Input scaling, integrates with DiffBind / DESeq2 / edgeR / csaw via sizeFactors and DiffBind library-size vectors, and applies the Patel et al 2024 *Nat Biotechnol* review's failure-mode framework to validate that normalization is correctly applied at the read level (not peak counts). Use when global signal shifts are expected (HDACi, BETi, EZH2i, dosage, target knockdown), when ChIPseqSpikeInFree detects post-hoc shifts, or when validating internal-control regions before publication.

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

Normalizes ChIP-seq data using exogenous spike-in (ChIP-Rx with Drosophila chromatin per Orlando 2014 / Egan 2016; E. coli carryover for CUT&RUN/CUT&Tag). Distinguishes RRPM from Rx-Input scaling, integrates with DiffBind / DESeq2 / edgeR / csaw via sizeFactors and DiffBind library-size vectors, and applies the Patel et al 2024 *Nat Biotechnol* review's failure-mode framework to validate that normalization is correctly applied at the read level (not peak counts). Use when global signal shifts are expected (HDACi, BETi, EZH2i, dosage, target knockdown), when ChIPseqSpikeInFree detects post-hoc shifts, or when validating internal-control regions before publication.

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

技術文書やエージェント向け指示ファイルを作成・レビューするスキル。READMEや貢献手順も調べ、説明の分かりやすさ、運用上の整合性、多言語版の差分を確認します。

• 技術文書を作成・更新したいとき
• READMEや文書の変更レビュー
• エージェント指示と貢献手順の整備

OpenClawの脆弱性報告を、公開済みのバージョンと信頼範囲の根拠で確認し、終了・継続・影響の絞り込みを判断して、管理者向けの返信案をまとめます。

• OpenClawの脆弱性報告を判断したいとき
• 公開版に不具合が残るか確認したいとき
• 既存の勧告との重複を調べたいとき

開発用スキルの初回利用に向けて、課題の管理先、仕分け用ラベル、用語集や設計判断の記録の配置を確認し、リポジトリ共通の設定文書を整えるスキル。

• 開発用スキルの初期設定
• 課題管理先と仕分けラベルの整理
• 用語集と設計判断の記録の配置決め

Gitの変更内容と過去の履歴を確認し、Conventional Commitsの形式やリポジトリの慣例に沿って、種類・対象範囲・長さを整えたコミット文案を作るスキル。

• コミット前にメッセージを書きたいとき
• 既存のコミット文を確認・修正したいとき
• プルリクエストの短い要約作成

メモや調査資料をもとに、ブログ記事、ガイド、ニュースレターなどの長文を作成し、既存の文体やブランドの方針に合わせて構成と根拠を整えるスキル。

• メモや文字起こしを記事に仕上げたいとき
• ブランドの文体に合わせた記事作成
• 実用的なガイドやチュートリアルの執筆

Webの電子署名画面で署名・日付・入力欄を数値座標で配置する手順をまとめたスキル。署名者ごとの欄の割り当てを確認し、送信前の下書き確認まで整理します。

• 生成した契約書に署名欄を準備したいとき
• 署名欄の担当者を確認したいとき
• 確認用の下書きと画像を残したいとき

XやLinkedInのつながりを現在の仕事や関心に合わせて見直します。整理・維持・追加の候補を理由付きで示し、本人の文体に合う連絡文の下書きまでまとめます。

• Xのフォロー解除候補を確認したいとき
• LinkedInのつながりを見直したいとき
• 今の関心に合うフォロー先を探したいとき

A retail sales-floor training on consultative selling — the flow, the role-plays, and the daily habit that lifts conversion. Built as a decision-grade professional training deck for store associates, floor managers.

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

Ensure async-path backend code that could block the asyncio event loop is protected by a teeth-verified runtime anchor in tests/blocking_io/. Use when changing backend Python under app/, packages/harness/deerflow/, or scripts/, when running a blocking-IO triage round over the whole repo, or when a reviewer/CI asks for blocking-IO coverage. Runs a deterministic scan (changed-lines or full-repo), routes each candidate, drafts/extends an anchor, and proves it fails when the blocking IO regresses.

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

Collaborative page-drafting mode for the OpenSpec docs. Builds a scratch plan inside the target page (purpose, structure, numbered draft steps), iterates on it with the user, then drafts one section per approved step and cleans up after itself. Use when a page needs a from-scratch rewrite or a new page is being shaped with the user in the loop.

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

Switches into OpenSpec docs-writing mode; loads the house style guide and drafts or revises pages in its voice (action-first, no preamble, scannable). Use when writing or editing pages in the OpenSpec docs tree.

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