「dr」の検索結果

Mine the day's sessions for the owner's intentions, cluster them into distinct ones, store them, and write two or three detailed posts with an explicit ask per channel, plus a loop tracking who answered. Drafts only. Triggers: "/intention", "mine today's intentions", "intention posts".

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

Onboard a new machine as a receive-only follower on a multi-machine agent network: it reads the shared vault, canon, skills and memory, runs nothing heavy locally (no RAG, reindex or GPU), and never receives executable hooks from the hub. Checklist-driven, with a verify step at each stage. Triggers: "/follower-onboard <machine>".

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

Write the follow-up after a call in the owner's own voice instead of a bot template: recall the transcript, person card and full correspondence, extract agreements with an owner and due date, draft short and personal, show before/after against the old template, then send through the approval gate and file the result to the person card. Triggers: "/fa", "follow-up", "what should I write to <name> after the call", or a fresh call transcript landing in the vault.

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

Check, search or digest Gmail across several mailboxes over the owner's own OAuth connector, with no browser and near-zero tokens for the raw pull. Read-only by default: drafting and sending go through the outbound approval gate. Triggers: "/gmail", "check mail", "any important emails", "find the email about <X>".

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

Publish an already-vetted post to a personal Facebook wall through the owner's real logged-in Chrome tab (a low-ban-risk path), rate-limit-guarded and draft-first: paste, verify what is actually in the composer, confirm after reload. Triggers: "/fb-post", "publish to facebook", "post this to my wall".

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

Read who commented on recent Facebook posts and publish personalized replies through the real logged-in Chrome tab, draft-first, with a daily cap and a minimum gap between replies. Triggers: "/fb-reply", "reply to my facebook comments".

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

After shipping a repo, release or feature, find who on GitHub actually needs it: search issues, discussions and catalogs for the symptom, rank live threads and draft one precise reply per consumer. Use right after any artifact goes public. Triggers: /consumer-hunt, /ch, find consumers, where to submit.

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

Spar with the founder as a synthetic cofounder on business questions (revenue, funnel, pricing, fundraising, debt, hiring, runway) with numbered objections and no flattery, arguing to consensus instead of agreeing. Not a coach and not a chatbot. Triggers: "/cofounder", or any strategic business question.

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

Scan recent agent sessions for content-worthy moments and capture them as drafts in a publishing funnel, publishing nothing. Zero-token detector, then a taste judge, then capture. Triggers: "/content-mine", "mine sessions for content", "what in our sessions deserves a post".

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

Drive the current task to a verified result instead of stopping at a plausible report. Use when the user says /continue, keep going, not done yet, push further, or is unhappy with the result. Rebuilds requirements from the conversation, re-checks real state, fixes root causes, verifies from the consumer side, offloads side quests.

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

Sync CRM knowledge notes in a vault with the live CRM code repositories: pull the read-only repos, detect which changed, and refresh only the affected reverse-engineering notes and the keep/drop/decide note. Triggers: "/crm-sync", "refresh CRM knowledge", "what changed in the CRM code".

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

Work the comments under published posts in one pass: list unanswered ones, reply only where a reply is genuinely expected (at most three per pass), name top commenters as warm-DM candidates, and prepare reply drafts on approval. Triggers: "/comments", "unanswered comments", "who is commenting".

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

Decision protocol for strategic work: recall the knowledge vault, run a gap analysis, emit a deep-research prompt for external tools, then synthesize the returned reports into a decision memo. Use before any new product, feature, market, pricing, GTM or architecture call, where local recall alone is not enough. Triggers: "/alfa-search-recall-deepresearch", "alpha protocol", "R+DR".

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

Finds free backlink and brand mention opportunities across Hacker News, Quora, GitHub, directories, and niche communities. Outputs a prioritized action plan with draft responses ready to post. Use after brand research and content creation to amplify reach and AI engine citations.

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

LLM-judge stage of an alpha-mining pipeline: take a miner's deterministic candidate list, keep only real signal, drop noise, and propose additions to that miner's curated note. Use after any zero-token detector run. Reads only the candidate digest and the home note, never the corpus. Triggers: "/alpha-judge <miner>", "judge the candidates".

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

Prose final-pass editor for GitHub issue bodies, pull request bodies, release notes, README/docs changes, public comments, and user-facing explanations. Use when Codex drafts or revises substantial prose that will be published or committed, especially when the user asks to polish, de-slop, make it less AI-written, improve a PR/issue body, or prepare docs text; do not use for ordinary code implementation, debugging transcripts, logs, quoted text, command output, API names, or Chinese conversational replies unless explicitly requested.

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

Audit, grade, rewrite, and issue funny evidence-backed tickets for generic AI-slop patterns in prose, social posts, UI/design, and code. Use when asked to de-slop writing, humanize AI copy, grade a draft, review a landing page or generated interface, remove vague claims and repetitive rhetoric, inspect AI-written code for generic abstractions and happy-path-only logic, or ticket someone for a specific quality offense. Do not use to determine whether AI authored something.

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

Use this skill when you need to review presentation materials from an audience perspective to improve their quality and effectiveness. Evaluates content clarity, visual design, logical flow, engagement factors, and Marp technical compatibility. Triggers include "review my presentation", "check my slides", "presentation feedback", or when a user has completed a draft presentation and wants comprehensive quality review.

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

Comprehensive data science workflow skill for analyzing tabular and time series data. Use when conducting exploratory data analysis, building predictive models, performing feature engineering, or generating data-driven insights. Supports end-to-end analysis from data understanding through model deployment, following industry best practices for regression, classification, time series forecasting, and statistical analysis.

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

Generic helpdesk first-response skill for creating KB-based response drafts. Use when handling support tickets, creating response templates, or building a structured helpdesk workflow. Supports error code detection, keyword matching, confidence scoring, multi-language templates, and escalation workflows. Customize by providing your own KB articles and configuration.

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

ビジネスコンテキストフロー（業務像モデル）を作成

Use when designing, evaluating, documenting, modernizing, reviewing, refactoring, or implementing software architecture and code-level structure, including requirements, context, architecture style selection, microservices patterns, WebAssembly/WASI/Component Model, UMA portable capabilities, runtime contracts, capability graphs, governed MCP/agent orchestration, clean code, code smells, Rust crate/library API architecture, Cargo feature/MSRV/SemVer policy, unsafe/FFI/no_std/library testing, modularity, views, NFR tactics, IAM/auth, security patterns, cost estimation, architecture-as-code fitness functions, ADR/RFC work, and engineering execution plans.

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

Use when evaluating, designing, drafting, revising, stress-testing, or preparing academic articles, empirical research reports, literature reviews, systematic reviews, meta-analyses, journal submissions, reviewer responses, research methods, sampling, measurement, analysis, publication readiness, or citation/source audits.

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

Concrete remediation proposal with Safe Harbour confidence — version bump, inline as first-party code, patch, workaround, or advisory. Use when applying a fix for a triaged CVE, evaluating fix-type trade-offs across registry / source / distro patches, producing rollback-safe manifest edits with dry-run verification, or generating a CycloneDX SBOM after the fix lands.

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