4,049 件 ・ 関連度順
概要と使いどころ
Use when a task needs the judgment of an Economics Teacher, Postsecondary — designing an intro micro/macro sequence for a mostly-terminal non-major audience, diagnosing a miskeyed or poorly discriminating exam item, calibrating TA grading on graphical or free-response problem sets, or investigating a spike in homework answers matching an online solution bank.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Communications Teacher, Postsecondary — designing or norming a multi-section basic public-speaking course, resolving a cross-rater grading discrepancy on a speech rubric, screening for and accommodating communication apprehension, or choosing a rhetorical-criticism method for a media-analysis assignment.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Business Teacher, Postsecondary — grading case analysis on the rigor of business reasoning rather than matching a single "correct" answer, updating stale textbook examples against current market conditions rather than teaching them as still-current, distinguishing taught analytical frameworks from personal business opinion presented as universal fact, and preserving the incomplete-information trade-offs of real business decisions rather than simplifying problems into false certainty.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Postsecondary Chemistry Teacher — grading a lab report where the numeric result misses the "expected" value but the methodology is sound, distinguishing a conceptual misunderstanding from an arithmetic slip on a problem set, deciding how much procedural freedom to give students on an open-ended lab, or vetting whether a demo/lab procedure is safe to run in this specific room.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Career/Technical Education Teacher, Postsecondary — defending a shrinking trade or health-science program against a cutback decision, backward-mapping a shop or lab curriculum to an industry credential's exam blueprint, resolving a competency-based grading dispute where a passing average hides a failed safety check-off, or setting the terms of an advisory-committee review or work-based-learning placement.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Postsecondary Art, Drama, or Music Professor — diagnosing a jury/crit score that contradicts a semester of formative work, building a studio-art or performance tenure dossier around exhibitions and productions instead of publications, staffing applied one-on-one lessons or crit sections between adjuncts and full-time faculty, running a structured critique, or deciding whether a failed barrier jury means a change of major.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a billing and posting clerk — generating an invoice against a rate/contract schedule, applying an incoming payment across multiple open invoices, processing a credit memo or adjustment, or investigating an aging-report discrepancy.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an Architecture Teacher, Postsecondary — running studio desk crits and final jury reviews, grading design work on process and constraint-response rather than rendering polish, separating a personal design-style opinion from an objective functional or code flaw during critique, and checking whether a studio brief's precedent set is stale relative to current construction and code practice.
日本語の概要は準備中です。原文の説明を表示しています。
Language-agnostic writing style guidelines covering structure, tone, rhetorical constraints, banned phrases, and review checks. Use when writing any kind of content in any language. Including blog posts, notes, technical articles, technical writing, chitchat, social media posts, etc., even when you are just sending a text message. Also use when reviewing or editing existing content for tone and style compliance. For Traditional Chinese (zh-TW) content, apply `chinese-content-writing-guideline` alongside this skill.
日本語の概要は準備中です。原文の説明を表示しています。
Language-specific guidelines for producing high-quality Traditional Chinese (zh-TW) content: script, full-width punctuation, spacing, forms of address, grammar constraints, and Taiwan terminology. Includes the no-calque rule against literal translations of English phrasal verbs such as 折入 for fold in. Use when writing any kind of Chinese content. Including blog posts, notes, technical articles, technical writing, chitchat, social media posts, etc., even when you are just sending a text message. Also use when reviewing or editing existing Chinese content for language and terminology compliance. Always apply `writing-style-guideline` alongside this skill for structure, tone, rhetorical constraints, and banned phrases.
日本語の概要は準備中です。原文の説明を表示しています。
Write SEO-optimized long-form articles targeting specific keywords using the They Ask You Answer Big 5 framework (Marcus Sheridan). Articles are categorized by Big 5 type (Cost, Problems, Versus, Best/Reviews, How-To) and structured accordingly. The "answer first" rule applies to every article. Use when the user asks for an SEO article, blog post for ranking, "rank for keyword X", organic content, search-optimized post, pillar page, or content for organic traffic. Includes keyword targeting, search intent matching, internal linking suggestions, and meta tags. For improving an existing article, see copy-review. For deciding what to write about, see social-calendar pillars and icp-research. For repurposing it, see content-repurposer.
日本語の概要は準備中です。原文の説明を表示しています。
Write long-form thought leadership articles, opinion pieces, industry POV essays, and CEO/founder bylines using the Made to Stick SUCCESs framework (Chip and Dan Heath). Use when the user asks for a long-form article, executive byline, opinion piece, industry POV, manifesto, "explain our point of view on X", or wants to publish an authority-building piece (1200-2500 words). Reads brand voice and positioning from knowledge/. For a short-form post, see linkedin-post. For the newsletter, see newsletter-writer. For improving an existing draft, see copy-review.
日本語の概要は準備中です。原文の説明を表示しています。
Write paid ad copy for LinkedIn, Google, Meta, and YouTube. Produces multiple variants per platform, each targeting a different Eugene Schwartz awareness level and Cialdini persuasion principle. Use when the user asks for ad copy, ad variants, "write LinkedIn ads", Google ads, Meta ads, paid social copy, ad headlines, or wants creative for a paid campaign. Reads brand voice, ICP, and positioning from knowledge/. For organic social posts, see linkedin-post or social-calendar. For the landing page the ad points at, see landing-page-writer. For testing variants, see ab-copy-writer.
日本語の概要は準備中です。原文の説明を表示しています。
Take one piece of long-form content (blog post, podcast, talk, article, newsletter) and turn it into a multi-channel asset pack using the STEPPS framework (Jonah Berger, Contagious) to make each derivative asset more shareable. Use when the user says "repurpose this", "turn this into LinkedIn/Twitter/etc", "atomize this", "break this down for social", "create derivative content from X", "make a content pack from this", or wants to maximize output from one input. Each channel is mapped to its strongest STEPPS element. Orchestrates linkedin-post, content-writer, and other skills. For writing the original anchor piece, see thought-leadership-writer or newsletter-writer. For scheduling the derivatives, see social-calendar.
日本語の概要は準備中です。原文の説明を表示しています。
Read and write Bluesky: view profiles and timelines, search posts, post, follow, read notifications. Trigger phrases: bluesky, atproto.
日本語の概要は準備中です。原文の説明を表示しています。
Post-writing SEO validation with pass/fail checklist covering title tag length and keyword placement, meta description quality, heading hierarchy and keyword density, internal/external link audit with anchor text analysis, canonical URL verification, Open Graph meta tags (og:title, og:description, og:image), Twitter Card validation, structured data presence and validity, URL structure optimization, and image alt text presence. Produces prioritized fix list with specific recommendations. Use for ONE finished post when the user says "seo check", "validate seo", "on-page seo", "title tag check", "link audit". Not for a whole-site audit (blog-audit, claude-seo), AI-citation scoring (blog-geo), schema generation (blog-schema), or the delivery gates (blog_preflight.py).
日本語の概要は準備中です。原文の説明を表示しています。
Measure writing-style statistics (sentence length, vocabulary, transitions, phrasing) from 5 to 10 posts you or your client wrote, and produce a voice profile for VOICE.md, blog-persona, and blog-write. Use for "learn my style", "build a writing baseline". It describes style; it does not detect or attribute authorship, and it is not for scoring a post (blog-analyze) or writing brand rules (blog-brand).
日本語の概要は準備中です。原文の説明を表示しています。
Suggest tags and categories for a blog post from its content, audit a site's tag and category health, and, only after the user approves a shown plan, sync tags and categories to WordPress, Shopify, Ghost, Strapi, or Sanity. suggest and audit are read-only; sync is dry-run by default and never deletes, merges, or edits post content. Use when the user says "tag suggestions", "taxonomy audit", "sync tags", "WordPress tags", "Shopify tags". Not for keyword research (blog-brief) or schema markup (blog-schema).
日本語の概要は準備中です。原文の説明を表示しています。
Translate existing blog posts into one or more target languages with SEO-optimized localization. Produces native-quality translations that preserve markdown structure, frontmatter, schema JSON-LD, image and chart embeds, and evidence-backed explanations. Localizes keywords, meta tags, numbers, dates, currencies, and quote styles per locale. Flags machine-translation artifacts for review. Run BEFORE blog-localize: this handles language conversion; localize handles cultural adaptation after translation completes. Use when user says "translate blog", "blog translate", "uebersetzen", "traduire", "traducir", "translate post", "blog auf Deutsch", "blog en espanol".
日本語の概要は準備中です。原文の説明を表示しています。
Read-only audit of a folder of existing multilingual blog posts: translation coverage, parity, hreflang and canonical consistency, meta-tag parity, and stale translations, with a prioritized report. Use when the user says "locale audit", "check translations", "multilingual audit", "hreflang check", "Uebersetzungen pruefen" about posts that already exist. Not for creating or fixing translations (blog-translate, blog-localize, blog-multilingual) or for a site-wide technical hreflang crawl (claude-seo seo-hreflang).
日本語の概要は準備中です。原文の説明を表示しています。
Create a content brief for ONE planned post: target and secondary keywords, search intent, template choice, competitor gaps from the live SERP, sourced statistics to include, section plan, internal-link targets, and distribution ideas. Use when the user says "content brief", "blog brief", "SEO brief", "article brief". Not a skeleton only (blog-outline), a multi-post plan (blog-strategy, blog-calendar, blog-cluster), or the article itself (blog-write).
日本語の概要は準備中です。原文の説明を表示しています。
Compare two Google Search Console page exports (current vs previous period) to flag pages whose clicks or impressions fell by a chosen threshold, with a triage hint (refresh, query shift, consolidate, prune). The 20% default is a screening heuristic, not proof of decay. Use for "/blog decay", "content decay", "QoQ decline", "refresh declining posts". Needs two GSC exports; not for diagnosing a single traffic drop live (blog-google) or rewriting posts (blog-rewrite).
日本語の概要は準備中です。原文の説明を表示しています。
Detect keyword cannibalization across blog posts by extracting primary keywords from titles and headings, clustering semantically similar targets, and flagging posts competing for the same search intent. Supports a free local mode (file analysis) and a paid DataForSEO API mode that runs only after the user approves the call count. Outputs a severity-scored report with merge or differentiate recommendations. Use when the user says "cannibalization", "keyword overlap", "competing pages". Not a site audit (blog-audit) or cluster planning (blog-cluster); it changes no files or redirects.
日本語の概要は準備中です。原文の説明を表示しています。
High Availability control plane for Yuzu — the canonical entry point for any work on ADR-2002 (active-active server tier, gateway-fronted routing, Postgres-backed coordination seam, HA Postgres storage). Use when the user says "/ha", "/high-availability", "/ha-matrix", asks to plan or implement an HA workstream (WS-0…WS-14), asks "what's our HA gap" or "is it safe to run a second replica yet", asks to audit HA readiness, or starts work touching the coordination seam (leader election / fenced epochs / transactional outbox), gateway intra-cluster routing, shared `AgentRegistry` presence, PKI/CA HA, or the `deploy/docker/*ha*` / `scripts/ha/` surface. The skill bundles the two-axis model, the safe-to-scale gate, the delivery matrix (current-state + reviewers + status), the per-workstream workflow, and the load order for the routed reference docs.
日本語の概要は準備中です。原文の説明を表示しています。