「search skill」の検索結果

Write cold outreach to potential clients that gets replies — specific, useful, and about them — instead of the templated pitch that gets deleted. Use when asked to write a cold email to a prospect, get clients through outreach, cold pitch help, or reach out to potential customers. Produces a researched, personalized message that leads with their problem, a clear low-friction ask, proof you're credible without bragging, a subject line, and a short follow-up sequence — plus who to target and what to avoid so it lands as a helpful note, not spam.

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

Negotiate a car purchase without getting played — know the real target price, handle the dealership tactics, and keep the financing and add-ons from eating your savings. Use when asked to help me negotiate a car, buy a car without getting ripped off, what should I pay for this car, or dealership negotiation tips. Produces a target-price approach (research the out-the-door price), the dealer tactics to expect and counters, guidance on separating price/trade/financing, the add-ons to decline, and a walk-away plan — flagging to verify current pricing and rates.

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

Plan an e-commerce category / collection page that ranks and merchandises well. Use when asked to design a category page, a PLP (product listing page), a collection page, or to improve category SEO and merchandising. Produces a brief — search intent & keywords, intro copy, merchandising/sort logic, filters & facets, internal links, and SEO/technical notes — so the page converts browsers and earns organic traffic.

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

Design the archive layer that keeps current workspaces lean without losing history — what moves, when, to where, findable-by-search, with the project-close ritual that makes archiving automatic instead of aspirational. Use when asked set up an archiving system, our workspace is drowning in old projects, when should things get archived, or make history findable without cluttering today. Produces the archive triggers, the destination structure, the findability rules, and the close-out ritual.

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

Set up and keep a job application tracker: one master CV, every tailored version, where each was sent, its status, next action and follow-up date, plus a weekly review of what is working. Use when asked to track my job applications, organise my job search, which CV did I send to which company, or what should I follow up on this week. Produces a tracker table (markdown or CSV) with one row per application, a version log linking each to its tailored CV, this week's actions, and a short weekly review of response rates by source.

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

Structure vague opportunities and unclear briefs into actionable one-page problem statements. Use when asked to clarify a vague brief, frame an undefined problem, make sense of an unclear opportunity, or when the user says 'we need to figure out what to do about X' or 'I've been asked to look into Y'. Produces a structured problem brief with reframed questions, scoped boundaries, and a minimum viable research plan.

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

Audit a content library, docs site, or blog for AI-generated filler that's eroding trust and search performance — and triage what to fix, rewrite, or delete. Use when asked to find slop in a content library, audit AI-written content quality, explain why content engagement or rankings dropped after scaling with AI, or set a quality bar for AI-assisted publishing. Produces an audited inventory with per-piece verdicts, the detection signals used, a triage plan, and a publishing quality gate that prevents recurrence. For a single article's AI-citability use aeo-optimizer; for the strategy itself use content-calendar or seo-content-brief.

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

Create learning paths for programming tools, and define what information should be researched to create learning guides. Use when user asks to learn, understand, or get started with any programming tool, library, or framework.

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

Search DigiKey for electronic components and download datasheets — primary source for prototype orders and the preferred API method for fetching datasheets. Find parts by keyword or MPN, check pricing/stock, download datasheets via API, analyze specifications. Sync and maintain a local datasheets directory — extract components from schematics, download missing datasheets, keep them up to date. Also supports batch MPN-list seeding (`--mpn-list`) for bulk workflows without a KiCad project. Use when the user asks about electronic components, part specs, datasheets, pricing, stock, footprints, or needs to download a datasheet — even without mentioning "DigiKey". Also for "sync datasheets", "download datasheets for my board/project", or mentions a datasheets directory. DigiKey is the default distributor for prototyping. For BOM workflows, see the bom skill.

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

Use this skill to build academic-style .docx output: journal / conference / thesis chapters carrying formal citation style (APA, Chicago, IEEE, MLA), numbered equations, figure & table cross-references, footnotes/endnotes, bibliography, or multi-column journal layout. Trigger on: 'research paper', 'journal paper', 'conference paper', 'manuscript', 'thesis', 'APA', 'MLA', 'Chicago', 'IEEE two-column', 'bibliography', 'hanging indent', 'citation style', 'abstract + keywords', 'equation numbering', 'cross-reference', paper with footnotes/endnotes. Output is a single .docx.

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

Use Ontoly Software Graph evidence, CLI reports, MCP, and official Ontoly Agent Skills before searching source files when reviewing architecture, dependencies, request flows, configuration, impact, or security-sensitive ownership.

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

Search DigiKey for electronic components and download datasheets — primary source for prototype orders and the preferred API method for fetching datasheets. Find parts by keyword or MPN, check pricing/stock, download datasheets via API, analyze specifications. Sync and maintain a local datasheets directory — extract components from schematics, download missing datasheets, keep them up to date. Also supports batch MPN-list seeding (`--mpn-list`) for bulk workflows without a KiCad project. Use when the user asks about electronic components, part specs, datasheets, pricing, stock, footprints, or needs to download a datasheet — even without mentioning "DigiKey". Also for "sync datasheets", "download datasheets for my board/project", or mentions a datasheets directory. DigiKey is the default distributor for prototyping. For BOM workflows, see the bom skill.

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

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.

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

Writes product-led content pages optimized for both search engines and AI engine citations. Produces markdown files with frontmatter, following page-type frameworks (comparison, guide, use case, learn, trust) with verified sources and no fabricated data.

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

Scaffold a minimal local Deep Agent in Python by following the official quickstart, using provider-native web search instead of Tavily. Use when the user wants to quickly build or try a Deep Agent locally.

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

Scaffold a minimal local Deep Agent in TypeScript by following the official quickstart, using provider-native web search instead of Tavily. Use when the user wants to quickly build or try a Deep Agent locally.

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

Use when planning or reporting the analysis for an American Educational Research Journal (AERJ) manuscript — multilevel/HLM and growth models, IRT/measurement, quasi-experimental estimation, or qualitative coding and thematic analysis. Analysis must meet the AERA reporting standards (warrant + transparency). Strengthens analysis reporting; it does not run models for you.

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

Use when writing the response to an American Educational Research Journal (AERJ) revise-and-resubmit. AERJ R&Rs come back through the handling editor and multiple masked reviewers, so the response must convert each reviewer while keeping the editor confident the revision is convergent. Structures the response letter; it does not fabricate new results.

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

Use when drafting or polishing an American Anthropologist (AA) manuscript so it reads across all four fields, follows AA house style (Chicago author-date; free-format submission accepted), fits the section word caps (Research Articles ≤ 8,000 words; abstract 200 words), and uses inclusive, care-ful language. Tightens prose and format; it does not invent content.

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

Use when running the final pre-submission preflight for American Anthropologist (AA) via the Research Exchange platform — section selection, anonymization, word/abstract caps, Chicago author-date (free-format accepted), DOIs, ORCID, ethics statement, and figure permissions/alt text. Final checks; it does not draft content.

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

Use when targeting Geology (GSA) or deciding whether a short, high-impact geoscience research letter fits this venue. Encodes the journal's broad-significance-in-tight-length fit, the novelty and rapid-communication bar, GSA house style, official-submission re-check, and desk-reject heuristics.

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

Use when drafting or polishing an Agricultural Systems (AgSy) manuscript so it reads clearly for a systems-science audience, follows the journal's format, and meets front-matter requirements (abstract <= 250 words, Highlights, graphical abstract). Research papers run to about 8,000 words (no hard cap). Tightens prose and format; it does not invent content.

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

Use when an Advanced Materials manuscript must be fit to its article-type format — Communication versus Research Article — where word count and display items are budgeted together against a typeset page limit. Manages the length budget; does not restructure the science or polish prose line by line.

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

Use when judging whether a research idea fits Administrative Science Quarterly (ASQ) and has the *surprising* theoretical insight ASQ demands. Sharpens the puzzle and the contribution claim; it does not design the study or write theory sections.

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