「make」の検索結果

Generate PDFs from LaTeX (.tex) or Markdown (.md) using Tectonic, a self-contained TeX engine. Use whenever the user wants a PDF, whether converting markdown, compiling existing LaTeX, writing a document from scratch (reports, resumes, letters, CVs), or live-rebuilding while the user edits. Trigger on words like "make a PDF", "convert to PDF", "render this markdown", "compile this tex", "latex", "tectonic", "typeset" — even when the tool is never named.

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

中文去 AI 腔一整套（装完即用，零 API Key —— 装了本 skill 的 agent 自己就是那个 LLM）。 六个流程：① 生成即去 AI —— 写中文时按本 skill 的写作指南落笔，初稿就不带 AI 腔； ② 复查改写 —— 产出后对照本 skill 的清单再过一遍，定点拆模板句式； ③ Python 词语替换 —— ./humanize replace 按文体自动路由词表（学术 120+ 条 / 通用 220+ 条），只做短语级、只在子句边界替换，改完自动核对数字/专名/段落； ④ Claude 腔转中文 —— 把 Claude 助手腔的中文改写成平实中文， 规则提炼自 gvzdv/claudish-to-english 并本地化； ⑤ 去水印 —— ./humanize watermark 扫清零宽字符/双向控制符/同形替身， 并对照 guillaumemeyer/watermarks-remover 说明统计水印的边界； ⑥ 纠错顺句 —— 修错词、病句、标点，拗口和用词不准处轻手顺一顺；改动范围有硬校验。 另有检测（0-100 分）、风格转换、学术降重等 CLI。 Use when user says: "去AI味", "降AIGC", "人性化文本", "humanize chinese", "AI检测", "AIGC降重", "去除AI痕迹", "文本改写", "论文降重", "知网检测", "维普检测", "AI写作检测", "让文字更自然", "detect AI text", "humanize text", "make text human-like", "去ai化", "改成人话", "去机器味", "长文本改写", "小说改写", "写一篇", "claudish", "去claude腔", "助手腔", "去水印", "watermark remover", "remove watermark"

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

Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.

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

ALWAYS use this skill when committing changes. Applies Shipfox agent sequencing for branch checks, scoped validation, and commit creation. Trigger on commit, commit changes, save changes, make a commit, or create commit.

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

ALWAYS use this skill when creating pull requests. Applies Shipfox agent sequencing for GitHub CLI review preparation and pull-request creation. Trigger on create PR, open PR, submit PR, make PR, push and create PR, or prepare changes for review.

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

Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.

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

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

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

A 15-minute guided setup that teaches Cowork who you are, how you work, and what tools you use — so every result feels tailored instead of generic. Use when setting up Cowork for the first time, for personalizing your workspace preferences, during onboarding after your first session, when configuring your tools and context, or when the user says "set up cowork", "configure cowork", "why is cowork giving me generic results", "cowork setup", "personalize cowork", "make cowork know me", "cowork feels like chatgpt", or "how do I get better results from cowork".

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

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

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

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

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

Validate at every layer data passes through to make bugs impossible

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

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

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

Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.

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

Make an out-of-session agent AgentOps-native via skills + ao CLI + CI, not hooks.

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

Use this skill whenever the user asks for an HTML-first visual design deliverable or design judgment: interactive prototype, slide deck, motion demo, infographic, dashboard, landing page, whitepaper, changelog, business card, social cover, brand system, design critique, multi-variant exploration, or export to MP4, GIF, PPTX, PDF, or SVG. It is optimized to make AI agents do the routing, template selection, verification, and export prep so humans spend less time prompt-engineering. Do not use for production web apps, SEO sites, backend systems, or pure copy edits.

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

Agent-native design engine that makes AI do more useful work: route the prompt, fork a template, weave IFQ ambient craft, verify the artifact, and only install export tooling when requested. One prompt -> shippable HTML, with optional MP4 / GIF / PPTX / PDF / SVG. Triggers include prototype, hi-fi mockup, slide deck, motion demo, infographic, dashboard, whitepaper, changelog, business card, social cover, brand from scratch, design critique, mp4/gif export, 60fps, keynote, PPTX, A-vs-B benchmark. Do not use for production web apps, SEO-critical sites, backend systems, or pure copy edits.

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

Create agent company packages conforming to the Agent Companies specification (agentcompanies/v1). Use when a user wants to create a new agent company from scratch, build a company around an existing git repo or skills collection, or scaffold a team/department of agents. Triggers on: "create a company", "make me a company", "build a company from this repo", "set up an agent company", "create a team of agents", "hire some agents", or when given a repo URL and asked to turn it into a company. Do NOT use for importing an existing company package (use the CLI import command instead) or for modifying a company that is already running in Galyarder Framework.

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

Generative Engine Optimization plus agent readiness. Use this skill whenever the user asks about GEO, AEO, LLMO, optimizing content for AI search engines (ChatGPT, Perplexity, Google AI Overviews, Claude, Gemini, Copilot), getting cited by LLMs, brand mentions in AI responses, llms.txt, robots.txt for AI crawlers, Schema.org JSON-LD, FAST framework, agent readiness, MCP server discovery, Web Bot Auth, OAuth for agents, API Catalog, agentic commerce (x402, ACP, UCP), Markdown content negotiation, or auditing a site or page for AI visibility. Also trigger when the user says "AI SEO", asks how to "rank in ChatGPT", "show up in Perplexity", "appear in AI Overviews", or wants a site to "speak to AI agents". Trigger even when the request is implicit, such as "review this article so AI search picks it up" or "make our docs agent-friendly".

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

Create, read, edit, and open draw.io (.drawio) files. Supports architecture diagrams, ER diagrams, flowcharts, domain model diagrams, and more. Use when requests include "create a diagram", "make a flowchart", "draw an architecture diagram", "create an ER diagram", "open a .drawio file", "what's in this diagram?", etc. Do NOT use for Mermaid or PlantUML generation.

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

"Apply Upper Echelons Theory (Hambrick and Mason, 1984) to analyze how top management team characteristics — demographics, experiences, values — shape strategic choices and organizational outcomes. Use this skill when the user needs to evaluate TMT composition effects on strategy, predict strategic direction from leadership profiles, assess whether managerial discretion enables or constrains executive influence, or when they ask 'does leadership background matter for strategy', 'how does TMT composition affect decisions', or 'why did this management team make that choice'.".

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

"Apply Transaction Cost Economics (Williamson, 1975, 1985) to analyze governance structure choices — market, hybrid, or hierarchy — based on transaction characteristics. Use this skill when the user needs to decide make-or-buy, evaluate outsourcing vs vertical integration, design governance mechanisms for inter-firm relationships, or when they ask 'should we build this in-house or outsource', 'why do firms vertically integrate', or 'how should we structure this partnership'.".

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

"Apply the Resource-Based View (Barney, 1991) and VRIO framework to evaluate whether a firm's resources and capabilities confer sustained competitive advantage. Use this skill when the user needs to assess internal resources for strategic value, determine if a competitive edge is sustainable, audit resource portfolios for VRIO criteria, or when they ask 'what makes our advantage sustainable', 'which resources matter most', or 'can competitors replicate this'.".

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

"Conduct a systematic literature review following the PRISMA framework with explicit search strategy, inclusion and exclusion criteria, quality assessment, and transparent synthesis. Use this skill when the user needs to design a reproducible literature search, apply PRISMA flow documentation, develop inclusion and exclusion criteria, assess study quality, or when they ask 'how do I do a systematic review', 'what is PRISMA', or 'how do I make my literature review reproducible'.".

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