스킬 찾기

Fill in a PDF form, annotate or redact a PDF, or add, remove or rotate its pages, when the office_edit tool is not available. Fills fillable and flat forms with the scripts FORMS.md walks through, puts notes and text on a page, blacks out words so they are gone from the file, and inserts, deletes and rotates pages with pypdf, qpdf or pdftk. Merging, splitting, creating, watermarking and encrypting PDFs are the pdf skill's.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use whenever a Word document (.docx), spreadsheet (.xlsx), slide deck (.pptx) or PDF in the workspace is to be written, filled in, edited or commented on and the office_edit tool is available: the user watches your edits appear live in the file pane, under your name, and may edit beside you. Covers drafting a document section by section, filling and formatting sheets, building slides in the Claude Slides format, and filling, redacting or annotating a PDF.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create, change or cancel a prompt that runs on a schedule, in whatever language the user asks. Use when the user says things like "every weekday at 8:30", "în fiecare zi lucrătoare la 8:30", "each morning", "remind me at noon", or wants to reschedule, edit or stop a scheduled task.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill when read_file is not enough to read a PDF — it failed, timed out, or returned garbled or empty text, or the question is about figures, charts, layout, embedded images, attachments, or form-field values. Covers content inventory, text extraction, page rasterization for visual inspection, embedded image/attachment/table/form-field extraction, and choosing the right reading strategy for different document types (text-heavy, scanned, slide-decks, forms, data-heavy). Do NOT use this skill for PDF creation, merging, splitting, watermarking, or encryption — use the pdf skill instead — nor to fill, annotate, redact or rotate: office_edit where the chat has it, else the pdf-forms skill.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Import a memory export from another AI assistant (ChatGPT, Gemini, Claude, etc.) into this agent's memory — conversationally, additively, and with the pasted content treated as data. Use when the user wants to bring over what another assistant knows about them.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Reflective pass over your memory — merge duplicates, fix stale facts, prune what no longer matters. Use when the user asks to clean up or review what you remember, or when memory has grown cluttered or contradictory.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

You MUST use this before any creative work — creating features, building components, drafting documents, designing workflows, or modifying behavior. Explores your human partner's intent, requirements, and design before any implementation begins.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when facing 2+ independent tasks or investigations that can be worked on without shared state or sequential dependencies — fan out to specialized sub-agents with isolated context, then synthesize the results.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when you have a written implementation plan to execute inline in the current session with review checkpoints. Prefer subagent-driven-development when sub-agent dispatch is available.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when creating new skills, editing existing skills, or verifying skills work before deployment. Applies Test-Driven Development to process documentation — watch agents fail without the skill, write the skill that addresses those failures, then close loopholes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Geocode, POIs, routes, timezones via OpenStreetMap/OSRM.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill to merge PDFs, split them apart, create new PDFs, add watermarks, encrypt or decrypt them, extract their tables or images, or OCR a scanned PDF to make it searchable. If the user asks to produce a .pdf file, use this skill.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

When the office_edit tool is available and the deck is a .pptx in the workspace, use the office skill instead: the user watches the slides arrive live. Use this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations as PowerPoint (.pptx) files; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email, summary, or creating a different type of slide deck); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user asks for a PowerPoint, a deck, slides or a presentation, or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

The Arbor research-coordinator protocol: the OBSERVE -> IDEATE -> SELECT -> DISPATCH -> DECIDE cycle over a durable Idea Tree. Preloaded automatically on /auto-research sessions. The coordinator never edits code or runs commands — executors do that in isolated worktrees; the coordinator steers the tree with idea_tree / dispatch_experiments / merge_experiment.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

The Arbor executor workflow: clone the repo from the git bundle your brief hands you, implement and evaluate exactly ONE hypothesis with the file tools, then report structured results via worker_complete. Preloaded automatically on arbor-executor task workers. Never touch the held-out test split.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

DECIDE-phase doctrine for an Arbor research run: when to merge, prune, combine, or finalize; how the held-out merge gate works; and the rule that the final report uses TEST scores. Load before deciding what to do with completed experiments.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Intake for an autonomous research run (Arbor). Use when the user wants to optimize a metric in a repo over many isolated experiments — 'optimize this benchmark', 'improve the model F1 overnight', 'beat the leaderboard'. Discovers the repo/eval/splits, measures the baseline, confirms a Research Contract, then emits a ready-to-send /auto-research command. Does NOT start the run itself.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when you have a spec or requirements for a multi-step task, before touching code or producing output. Turns a design into bite-sized, copy-pasteable tasks with exact paths and complete code.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", or "switch to --preset".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Decomposition playbook and anti-temptation rules for an orchestrator agent that routes work through the Surogates subagent task layer. Pair this skill with an AgentDef whose tool filter strips the implementation tools (terminal, file, web, code) — that's how 'don't do the work yourself' is enforced structurally, not just behaviorally.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Hard-gated ideation for an Arbor research run. Load at the START of every IDEATE round, before drafting any hypothesis. Enforces the PI mindset (mechanism over knob), the four-question first-principles probe, the kill-filter, and the four-line hypothesis format. Ported from Arbor's idea_drafting + first_principles_probe.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

When the office_edit tool is available and the spreadsheet is a .xlsx in the workspace, use the office skill instead: the user watches the edit live. Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.