「org」の検索結果

Design AI governance frameworks for organizations. TRIGGERS - Use when user needs help with ai-governance-framework related tasks.

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

Manage change for AI adoption in organizations. TRIGGERS - Use when user needs help with ai-change-management related tasks.

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

Create acceptable use policies for AI tools within organizations. TRIGGERS - Use when user needs help with ai-acceptable-use-policy related tasks.

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

Implement 5S workplace organization. TRIGGERS - Use when user needs help with 5s-implementation related tasks.

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

When the office_edit tool is available and the document is in the workspace, use the office skill instead: the user watches the edit live. Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx) or Word templates (.dotx). Triggers include: any mention of Microsoft Word Documents, such as 'Word doc', 'word document', '.docx', '.dotx', 'microsoft doc'. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a deliverable as a Word or .docx file (to download, email or print), use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or coding unrelated to document generation.

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

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.

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

Use when the user wants a complete SPSS or SPSS-MCP empirical research workflow: organize source data, prepare datasets, design variables and models, run SPSS analyses, export Chinese result paragraphs and tables, write a Chinese LaTeX paper, and compile the final PDF.

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

Sets up a complete per-client workspace in Cowork with isolated context, preferences, deliverable templates, running notes, decision log, and automatic status reporting. For consultants, agencies, and professional services. Useful when onboarding a new client, during engagement kickoffs, for organizing existing client relationships, and when multiple clients need isolated context. Use when the user says "set up a client", "new client project", "client system", "client context", "client workspace", or "onboard a client".

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

Sets up a file-based memory system so Cowork always knows who you are, how you work, and where your projects stand. For eliminating repetitive re-introductions at session start, when building persistent context across multiple projects, or during initial Cowork onboarding. Use when the user says "claude doesn't remember me", "memory system", "persistent context", "why does it forget", "remember my preferences", "I keep re-explaining myself", or "how do I make Claude remember things".

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

Teaches you how to break large tasks into stages, save your place between sessions, and recover smoothly when a task gets interrupted. Use when planning a multi-day project, for breaking down large work into manageable stages, during recovery from an interrupted session, when managing complex ongoing work, or when the user says "cowork stopped in the middle", "token limit", "task too large", "context management", "how to do big tasks", "session got cut off", "cowork forgot what we were doing", "how do I work on something over multiple days", "it lost track of the project", or "my task is too big for one session".

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

Use when you need to hunt in the organisation's own Microsoft Sentinel workspace — sweep the logs for IOC hits (IP, domain, hash, URL, account), hunt behavioural TTPs from MITRE ATT&CK techniques, run KQL against live data, or check which tables the workspace actually ingests. Discovers available tables first and only generates KQL for tables that verifiably exist, so hunts adapt to each environment's connectors. Commonly chained by the /*-investigation skills to answer "were we exposed?". Reads $SENTINEL_TENANT_ID, $SENTINEL_CLIENT_ID, $SENTINEL_CLIENT_SECRET, $SENTINEL_WORKSPACE_ID. Read-only.

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

Use when you need to check whether an organisation/domain has been claimed by a ransomware group, profile a specific ransomware group (TTPs, leak-site infra, IOCs, YARA), or aggregate ransomware victim claims by country/sector/timeframe. Backed by ransomware.live's leak-site scrapes — 27k+ victims across 330+ groups. Commonly invoked by /domain-investigation, /ransomware-ecosystem, /threat-actor-profiling, and detection-engineering workflows. Reads $RANSOMWARE_LIVE.

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

Frontend development guidelines for React/TypeScript applications. Modern patterns including Suspense, lazy loading, useSuspenseQuery, file organization with features directory, MUI v7 styling, TanStack Router, performance optimization, and TypeScript best practices. Use when creating components, pages, features, fetching data, styling, routing, or working with frontend code.

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

Use SmokingGun to find complexity candidates and organize imported optimization evidence.

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

Expert in designing, orchestrating, and managing multi-agent systems (MAS). Specializes in agent collaboration patterns, hierarchical structures, and swarm intelligence. Use when building agent teams, designing agent communication, or orchestrating autonomous workflows.

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

Generated by Gremlin Forge Meta-Agent 🍆👾⚡

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

Remove AI-writing tells from README, docs, and user-facing text. Must be done line-by-line, no regex. Use after agents write any user-visible prose.

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

Deep code review after beads have landed — random exploration + cross-agent review, alternating. Use every 30–60 min during active implementation, or after any epic lands.

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

End-of-session ritual — close finished beads, file new ones for remaining work, run verify, commit in logical groupings, push. Work is not complete until git push succeeds.

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

Polishing pass over all open beads. "Check your beads N times, implement once." Run 4–6 times. Use after /plan-to-beads and between refinement rounds.

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

Remove telltale AI-writing patterns from README, docs, and user-facing text. Must be done line-by-line, manually. No regex. Use after agents write any user-visible prose.

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

End-of-session ritual. Close finished beads, file new ones for remaining work, run verify, commit in logical groupings, push. Work is not complete until git push succeeds.

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

Polishing pass over all open beads. Run 4–6 times. "Check your beads N times, implement once." Use after plan-to-beads and between refinement rounds.

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

Translate a polished markdown plan into self-contained beads in .beads/beads.jsonl. Treat this as a distinct translation problem, not task extraction. Use after /plan-synthesize produces a stable hybrid plan.

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