「consul」の検索結果

Multi-step content production pipeline that takes a topic or brief and produces a full blog post, email newsletter excerpt, and three social posts — all in your voice. Useful for building a content batch, when repurposing a core idea across formats, during content sprint sessions, and for turning expertise into publishable material. Use when the user says "create content", "content pipeline", "blog to social", "write and repurpose", "content engine", or "create a blog post and social posts".

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

End-to-end meeting workflow skill. Pre-meeting: research attendees, build agenda, prepare talking points, create pre-read. Post-meeting: process notes into action items, draft follow-up emails, log decisions, update project notes. Useful for preparing for important calls, during post-meeting processing, when following up with attendees, and for building a running decision log. Use when the user says "prepare for meeting", "meeting prep", "process meeting notes", "meeting follow up", "meeting machine", or "prep for my call".

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

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".

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

Shows you how to use Cowork's parallel workers to run multiple tasks at the same time instead of one after another — dramatically cutting the time on batch work. For processing large batches of files or research tasks, when running multiple independent analyses simultaneously, or during a performance optimization session. Use when the user says "speed up", "parallel workers", "batch task", "process multiple files", "why is cowork so slow", "faster", "do several things at once", or "can cowork multitask".

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

Cross-tool weekly intelligence briefing that pulls from your calendar, email, Slack, and tasks to produce a comprehensive pulse on what happened and what is coming. Useful for reviewing your week, during end-of-week wrap-ups, for preparing Monday priorities, and when catching up after time away. Use when the user says "weekly pulse", "weekly briefing", "week summary", "what happened this week", "weekly review", or "business pulse".

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

Discover what Cowork can do for YOUR specific role and tasks, for mapping your daily work to Cowork capabilities. Use when exploring what Cowork offers, for planning your Cowork adoption, during onboarding and role discovery, when figuring out where to start, or when the user says "what can cowork do", "what is cowork", "show me cowork features", "how can cowork help me", "what should I use cowork for", or "cowork capabilities".

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

Customize any Cowork skill or workflow to match your specific industry, company, and style. For tuning default skill outputs to your voice, when adapting generic workflows to a specific industry, or during a skill quality review. Use when the user says "customize this skill", "output is too generic", "make this work for my industry", "personalize this workflow", "results do not match my style", or "how do I get better results from Cowork".

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

Builds a personal voice profile so Cowork writes the way you write — not like a generic AI. Use when personalizing your writing style, for capturing your communication patterns and tone, during setup after getting generic-sounding output, when training Cowork to match your voice, or when the user says "teach claude my voice", "my writing style", "output doesn't sound like me", "brand voice", "personalize output", "make it sound like me", "it sounds too formal", "it sounds too robotic", "can cowork match my tone", or "how do I get cowork to write like me".

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

See the difference between Chat and Cowork with a live side-by-side comparison for understanding why Cowork is built differently. Use when evaluating AI tools, for comparing chat versus agent capabilities, during an AI tool decision, when switching from ChatGPT or Claude Chat, or when the user says "what is different about cowork", "cowork vs chat", "why not just use chatgpt", "show me the difference", "compare chat and cowork", or "why should I use cowork instead of chat".

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

Takes a repeating task from your work, breaks it into Cowork steps, and builds it into a documented, reusable workflow — optionally turning it into a custom skill. For converting manual repeating tasks into automated systems, when documenting a process for consistent execution, or during a productivity overhaul. Use when the user says "build a workflow", "automate my process", "I do this every week", "create a system", "repeating task", "I keep doing the same thing", or "make this a workflow".

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

Audits your Cowork setup across five categories, scores each one, and gives you a prioritized improvement plan. For reviewing how well you are using Cowork, when optimizing your workspace configuration, or during a quarterly productivity review. Use when the user says "health check", "am I using cowork right", "optimize my setup", "cowork audit", "what am I missing", "is my setup good", or "how do I get more out of cowork".

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

A zero-risk first Cowork experience for discovering what Cowork does differently. Use when onboarding to Cowork, for getting started safely, during first-time exploration, when starting fresh with a new AI tool, or when the user says "I am new to Cowork", "first task", "show me what Cowork does", "what can you do that Chat cannot", "help me get started", or "safe first task".

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

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".

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

Sets up safe working habits and a change log so you always know what Cowork has done to your files — and can undo anything. Use when setting up file protection guardrails, for establishing safe automation habits, during initial access configuration, when granting file permissions for the first time, or when the user says "is cowork safe", "file safety", "what if it deletes my files", "audit trail", "safety setup", "I'm nervous about file access", "how do I trust cowork with my files", "can cowork mess up my computer", "I heard someone lost files", or "how do I stay in control".

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

Interviews you about a task you repeat often, then walks you through building a custom skill for it using Cowork's built-in skill creator — no coding required. For packaging a repeating workflow into a one-phrase trigger, when teaching Cowork your personal process from scratch, or during a skill library build session. Use when the user says "create a skill", "teach claude my workflow", "custom skill", "make cowork do this automatically", "automate my process", "I do this every week", or "how do I make a skill".

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

Use the hyalo CLI instead of read/edit/grep/write when working with markdown (.md) files that have YAML frontmatter. This skill MUST be consulted whenever pi is working with markdown documentation directories, knowledgebases, wikis, notes, Obsidian-compatible collections, Zettelkasten systems, iteration plans, or any collection of .md files with frontmatter. Trigger this skill when: searching or filtering markdown files by content, tags, or properties; reading or modifying YAML frontmatter; managing tags or metadata across documents; toggling task checkboxes in markdown; getting an overview of a documentation directory; querying document properties or status fields; bulk-updating metadata across many markdown files; or when you find yourself repeatedly using read/edit/grep/write on .md files. Even if the user does not mention "hyalo" by name, use this skill whenever the task involves structured markdown documents with frontmatter. For pi sessions, ALWAYS use `--format text` for compact, LLM-friendly output.

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

Walk through the Designer/Developer wrap-up checklist for offboarding a client engagement — conversationally, one item at a time.

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

Write a client update — identify what was done, what's next, and surface risks before they become surprises. End of day, start of day, or end of week.

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

Strict red-green-refactor TDD workflow for implementing features, fixing bugs, or changing behavior in Rails applications. Enforces the discipline of writing a failing test before any production code. Use whenever you want to implement with TDD — whether a new feature, a bugfix, a refactor, or any behavior change.

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

Prepare to deliver difficult technical news to a client — a conversational prep session before the hard conversation happens

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

Think out loud about a problem, decision, or approach — Socratic friction to help you find clarity, not sympathy

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

Discover how a codebase already handles a specific concern — search broadly, find every instance, and assess consistency. The "how does this app do X?" tool.

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

Take one new feature slice from idea to reviewed, committed code in a single guided pass — scope it into the smallest shippable slice, build it test-first with strict TDD, review and fix the diff, then commit it. Chains slice → test-driven-development → the built-in /code-review → git-commit. Not for reviewing an existing PR, upgrades, or open-ended design questions.

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

Pressure-test an assumption, decision, or inherited constraint — Socratic cross-examination that forces you to defend or abandon your position

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