「cro」の検索結果

Plan a monthly content calendar across channels using the Content Marketing Matrix (Dave Chaffey, Smart Insights) - Entertain/Inspire/Educate/Convince. Every post gets a quadrant label. The monthly calendar must hit 40% Educate, 40% Inspire+Convince, 20% Entertain. Produces a week-by-week posting schedule with topics, formats, channels, and asset links. Use when the user says "content calendar", "social calendar", "plan next month's content", "what should we post", "content plan", "editorial calendar", "schedule posts for the month", or wants a structured posting plan for LinkedIn, Twitter, email, or blog. Reads brand voice, ICP, and past learnings from knowledge/. For writing the individual posts, see linkedin-post, newsletter-writer or content-writer. For the campaign this sits inside, see campaign-brief. For the end-of-month review, see retro.

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

Synthesize sprint retrospective notes into categorized action items and patterns. Use this skill when: - You have sprint retro notes (raw text, meeting transcript, or structured notes) to process - You need to identify recurring patterns across multiple retros - You want categorized action items with owners and deadlines from retro discussions

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

Allocate testing effort based on risk and failure likelihood using Google's SET/SWE/TE model. Use when user says "risk-based testing", "where should I focus testing", "test coverage strategy", "prioritize what to test", "high risk areas", or needs to decide how to distribute QA effort across a codebase - even if they don't explicitly say "risk-based".

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

Write landing page copy for product pages, campaign pages, lead-gen pages, pricing pages, and feature pages. Use when the user asks for landing page copy, product page, lead magnet page, "write the page for X", pricing page copy, feature page, hero section, or web copy that converts. Uses the StoryBrand SB7 framework (Donald Miller) to structure every page. Reads brand voice, positioning, and ICP from knowledge/. For improving an existing page's copy, see copy-review. For diagnosing why a page does not convert, see page-cro. For the ads driving traffic to it, see ad-campaign-writer.

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

Design and document a marketing growth experiment. Use when the user says "run a growth experiment", "test this channel", "growth test", "I want to experiment with [channel]", "traction experiment", "acquisition experiment", "let's test if [channel] works for us", "bullseye framework", "which channels should we try", "run a traction test", or wants to systematically test a marketing or acquisition channel before committing budget. For page-level conversion hypotheses, see page-cro. For copy variants to test, see ab-copy-writer. For recording the result, see retro.

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

Review and improve marketing copy that already exists - a page, an email, an ad, a post, a deck slide - using a fixed six-pass edit. Produces a marked-up diagnosis, a rewritten version, and a per-pass score so the user can see what changed and why. Use when the user says "review this copy", "improve this", "make this better", "tighten this", "edit this page", "does this copy work", "why is this flat", "punch this up", "proofread", or pastes existing copy and asks for feedback. Also use when copy is on-brand but underperforming. For writing new copy from nothing, see content-writer or landing-page-writer. For diagnosing a page's conversion problem beyond its words, see page-cro. For voice consistency rules, see brand-context.

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

Generate A/B copy variants grounded in Eugene Schwartz's awareness and market-sophistication stages and John Caples' tested-headline discipline. Every variant declares its angle, the awareness stage it targets, and a falsifiable hypothesis, and the skill recommends which pair to test first and what delta counts as signal. Use when the user says "A/B test this", "write variants", "give me options", "test different angles", "copy variants", "ab copy", "test this headline", "multiple versions", "which version is better", or wants to test copy before publishing. For reviewing copy that already exists, see copy-review. For sample size and stopping rules, see growth-experiment. For diagnosing a page rather than its words, see page-cro. For full paid ad sets by platform, see ad-campaign-writer.

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

Build a structured Quarterly Business Review deck for a customer account. Use when user says "QBR", "quarterly business review", "prep my QBR", "build the deck", "renewal prep", "executive check-in", "90-day review", or "customer business review" - even if they don't use the acronym. Applies to CSMs preparing for executive-level customer meetings focused on value delivered, health, and next quarter alignment.

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

Configure and control the claude-bionify bionic reading plugin. Use when the user asks about bionic reading settings (fixation/strength, boundary, minimum word length, acronyms, URLs, headings), wants to turn the bionic display on, off, or toggle it, asks for the current status, or asks how to use the /claude-bionify commands.

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

Audit technical SEO across crawlability, indexability, security, URLs, mobile, Core Web Vitals, rendering, structured data, and IndexNow. Exclude content strategy and backlinks.

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

**WORKFLOW SKILL** — Understand before implementing. USE FOR: any task where the agent might rush to code — forces understanding WHY/WHAT FOR/FOR WHOM before defining a solution, activates planning and reasoning discipline, prevents technical debt from shallow requests. Use to validate intent, plan before coding, reason before acting, challenge assumptions, prevent premature implementation. DO NOT USE FOR: deep multi-technology analysis (use contextação), persisting decisions across tasks (use task-map).

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

**WORKFLOW SKILL — MANDATORY for ANY hook work.** Create, configure, edit, debug, or review lifecycle hooks for VS Code Copilot (default) and Claude Code. USE FOR: criar/configurar/editar hook, hook do Copilot/Claude/agente, lifecycle hook, PreToolUse, PostToolUse, SessionStart, SubagentStop, Stop hook, UserPromptSubmit, PreCompact, bloquear comando, validar tool call, injetar contexto, guard, .agent.md frontmatter hooks, hooks.json, .github/hooks, .claude/settings.json, hook Node.js, cross-platform, hook não dispara/silencioso/ignorado, permissionDecision, hookSpecificOutput, additionalContext. **DEFAULT = VS Code GitHub Copilot.** Switch to Claude Code only when user explicitly says "Claude" OR workspace has `.claude/`. NEVER assume Claude. DO NOT USE FOR: general coding, creating agents (use agent-creator), creating skills (use skill-creator).

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

Initialize, adopt, and route work for a separate Obsidian knowledge vault through the portable claude-obsidian core. Use for vault setup, scaffolding, workspace selection, cross-project configuration, or choosing the correct wiki sub-skill. Triggers: /wiki, set up wiki, scaffold vault, create knowledge base, adopt this vault, Obsidian vault, second brain setup, persistent wiki.

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

Generate JSON-LD for ONE blog post (BlogPosting with Person, Organization, BreadcrumbList, ImageObject, VideoObject; FAQPage only as optional entity markup) in a single @graph, and check it against Google's current structured data support. Use when the user says "generate schema", "json-ld for this post", "blog schema". Not for auditing schema across a whole site or other schema types (claude-seo seo-schema), not for product pages, and not a promise of rich results: FAQ rich results ended 2026-05-07.

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

Analyze one supplied URL across on-page, content, technical metadata, schema, images, and performance. Use only for a single-page review.

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

Analyze ecommerce SEO across product pages, product schema, Shopping visibility, marketplace signals, and keyword gaps. Use only for stores, catalogs, or product listings.

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

Audit paid-ad copy, images, video, hooks, concepts, format coverage, platform-native fit, message match, creative fatigue, accessibility, and policy across supported platforms. Use for creative audit, ad creative, creative fatigue, creative diversity, ad copy review, video review, image review, or production priorities.

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

Score one blog post (or a folder of posts) on a 5-category 100-point scale covering content quality, SEO, E-E-A-T, technical elements, and AI citation readiness. Runs the deterministic analyzer first, then adds judgment and prioritized Critical/High/Medium/Low fixes. Advisory style diagnostics never infer authorship or affect the score. Exports markdown, JSON or table; works with MDX, markdown, HTML or a URL. Use when the user asks to analyze, score, rate or check the quality of specific posts ("analyze blog", "blog score", "check blog quality", "rate this post"). For a site-wide health check (orphan pages, cannibalization, stale content, schema across all posts) use blog-audit instead.

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

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.

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

Establish durable brand and voice context for cross-skill consumption. Generates BRAND.md (audience, positioning, do/don't editorial rules, taboo phrases, competitor differentiation) and VOICE.md (existing persona JSON re-expressed as readable prose), both written to the project root. When present, the blog orchestrator loads these files, fenced as untrusted data, for write, rewrite, brief, outline, calendar, and strategy workflows. Pairs with blog-persona, which manages the structured persona JSON. Use when the user says "blog brand", "create brand context", "BRAND.md", "VOICE.md", "establish editorial brand". Not for learning a voice from existing posts (blog-style) or managing persona JSON (blog-persona).

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

Monitor paid-ad account pacing, delivery, performance, creative fatigue, tracking, policy, and data quality across supported platforms. Use for daily or weekly checks, anomaly review, budget pacing, post-launch verification, or campaign monitoring.

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

Full-site blog health assessment scanning all blog files for quality scores, orphan pages, topic cannibalization, stale content, and AI citation readiness. Runs canonical batch analysis before site-wide checks. Produces per-post scores and a prioritized action queue. Use when the user asks for a site-wide blog health check across many posts ("blog audit", "blog health", "audit all posts", "site audit of the blog"). For one post, or a quality score with fixes for a few named files, use blog-analyze instead.

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

Research what people are actually saying about a topic in the last 30 days across Reddit, X / Twitter, YouTube, Hacker News, dev.to, Medium, and other public discourse platforms. API-free; uses WebSearch with platform-targeted site operators plus recency filters. Produces DISCOURSE.md (a structured brief) and JSON output the writer can consume. Complements blog-researcher (which focuses on authority sources) with a recency-and-engagement lens. Not for verifying statistics (blog-factcheck) or gathering authority sources. Use when user says "blog discourse", "discourse research", "what are people saying about", "research what people are saying", "voice of customer", "social listening", "30-day research", "trend research", "what's the discussion on", "real-time research", "practitioner discourse", "/blog discourse".

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

Stops defensive writing across the entire paper lifecycle — writing, revising, cutting, and organizing experiments. Treats the paper as a press conference, not a project summary, lab log, or self-audit: identify the single most publishable strength of the work and build the most favorable, complete, and persuasive narrative around it. Never present everything evenly, never volunteer weakness, never write an experiment diary, never attack the paper on the reviewer's behalf. Triggers: polish my paper, revise manuscript, write abstract, write introduction, write conclusion, shorten paper, rebuttal, respond to reviewers, organize experiments, defensive writing, AI-flavored academic writing.

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