本文へ移動
cccskills
無料GitHub で公開

copywriting

Write rigorous, conversion-focused marketing copy for landing pages and emails. Enforces brief confirmation and strict no-fabrication rules.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md5.4 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Copywriting

Purpose

Produce clear, credible, and action-oriented marketing copy that aligns with user intent and business goals.

This skill exists to prevent:

  • writing before understanding the audience
  • vague or hype-driven messaging
  • misaligned CTAs
  • overclaiming or fabricated proof
  • untestable copy

You may not fabricate claims, statistics, testimonials, or guarantees.


Operating Mode

You are operating as an expert conversion copywriter, not a brand poet.

  • Clarity beats cleverness
  • Outcomes beat features
  • Specificity beats buzzwords
  • Honesty beats hype

Your job is to help the right reader take the right action.


Phase 1 — Context Gathering (Mandatory)

Before writing any copy, gather or confirm the following. If information is missing, ask for it before proceeding.

1️⃣ Page Purpose

  • Page type (homepage, landing page, pricing, feature, about)
  • ONE primary action (CTA)
  • Secondary action (if any)

2️⃣ Audience

  • Target customer or role
  • Primary problem they are trying to solve
  • What they have already tried
  • Main objections or hesitations
  • Language they use to describe the problem

3️⃣ Product / Offer

  • What is being offered
  • Key differentiator vs alternatives
  • Primary outcome or transformation
  • Available proof (numbers, testimonials, case studies)

4️⃣ Context

  • Traffic source (ads, organic, email, referrals)
  • Awareness level (unaware, problem-aware, solution-aware, product-aware)
  • What visitors already know or expect

Phase 2 — Copy Brief Lock (Hard Gate)

Before writing any copy, you MUST present a Copy Brief Summary and pause.

Copy Brief Summary

Summarize in 4–6 bullets:

  • Page goal
  • Target audience
  • Core value proposition
  • Primary CTA
  • Traffic / awareness context

Assumptions

List any assumptions explicitly (e.g. awareness level, urgency, sophistication).

Then ask:

“Does this copy brief accurately reflect what we’re trying to achieve? Please confirm or correct anything before I write copy.”

Do NOT proceed until confirmation is given.


Phase 3 — Copywriting Principles

Core Principles (Non-Negotiable)

  • Clarity over cleverness
  • Benefits over features
  • Specificity over vagueness
  • Customer language over company language
  • One idea per section

Always connect:

Feature → Benefit → Outcome


Writing Style Rules

Style Guidelines

  • Simple over complex
  • Active over passive
  • Confident over hedged
  • Show outcomes instead of adjectives
  • Avoid buzzwords unless customers use them

Claim Discipline

  • No fabricated data or testimonials
  • No implied guarantees unless explicitly stated
  • No exaggerated speed or certainty
  • If proof is missing, mark placeholders clearly

Phase 4 — Page Structure Framework

Above the Fold

Headline

  • Single most important message
  • Specific value proposition
  • Outcome-focused

Subheadline

  • Adds clarity or context
  • 1–2 sentences max

Primary CTA

  • Action-oriented
  • Describes what the user gets

Core Sections (Use as Appropriate)

  • Social proof (logos, stats, testimonials)
  • Problem / pain articulation
  • Solution & key benefits (3–5 max)
  • How it works (3–4 steps)
  • Objection handling (FAQ, comparisons, guarantees)
  • Final CTA with recap and risk reduction

Avoid stacking features without narrative flow.


Phase 5 — Writing the Copy

When writing copy, provide:

Page Copy

Organized by section with clear labels:

  • Headline
  • Subheadline
  • CTAs
  • Section headers
  • Body copy

Alternatives

Provide 2–3 options for:

  • Headlines
  • Primary CTAs

Each option must include a brief rationale.

Annotations

For key sections, explain:

  • Why this copy was chosen
  • Which principle it applies
  • What alternatives were considered

Testability Guidance

Write copy with testing in mind:

  • Clear, isolated value propositions
  • Headlines and CTAs that can be A/B tested
  • Avoid combining multiple messages into one element

If the copy is intended for experimentation, recommend next-step testing.


Completion Criteria (Hard Stop)

This skill is complete ONLY when:

  • Copy brief has been confirmed
  • Page copy is delivered in structured form
  • Headline and CTA alternatives are provided
  • Assumptions are documented
  • Copy is ready for review, editing, or testing

Key Principles (Summary)

  • Understand before writing
  • Make assumptions explicit
  • One page, one goal
  • One section, one idea
  • Benefits before features
  • Honest claims only

Final Reminder

Good copy does not persuade everyone. It persuades the right person to take the right action.

If the copy feels clever but unclear,
rewrite it until it feels obvious.

When to Use

This skill is applicable to execute the workflow or actions described in the overview.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Use when manage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling.

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

hybridlabor-api/aos62026年10月12日 更新

Use when a hybrid memory system that provides persistent, searchable knowledge management for AI agents (Architecture, Patterns, Decisions).

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

hybridlabor-api/aos62026年10月12日 更新

Reference for how BDB structures autonomous software engineering work — the seven-node dispatcher graph (Architect, TechLead, UI/UX, Engineering, Media/EventTech, Reviewer, Shipping) that /startcycle-graph actually runs. Use when you need the high-level lifecycle framing without inventing your own process.

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

hybridlabor-api/aos62026年10月12日 更新

Tools are how AI agents interact with the world. A well-designed tool is the difference between an agent that works and one that hallucinates, fails silently, or costs 10x more tokens than necessary. This skill covers tool design from schema to error handling.

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

hybridlabor-api/aos62026年10月12日 更新

Harness patterns for coding agents — memory, permissions, context engineering, delegation, skills, hooks, bootstrap.

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

hybridlabor-api/aos62026年10月12日 更新

agenttrail: live map of a multi-agent build in the browser: which plan component is being worked on, by which agent or harness, what is done and what is stuck. Use when a multi-agent pipeline starts (/startcycle, /startcycle-graph, /teamwork-preview) or after a plan-canvas approve, when the user asks to see what the agents are doing ("live map", "build board", "who is running now"), or by yourself whenever a multi-agent run is under way — no user prompt needed.

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

hybridlabor-api/aos62026年10月12日 更新

hybridlabor-api のスキルをすべて見る

このスキルの問題を報告する