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

suede-content-strategy

Suede-owned content-strategy discipline for audience questions, content pillars, topic clusters, editorial priorities, cadence, distribution, refreshes, and stop-doing decisions. Use when deciding what to publish, why it deserves resources, and how the portfolio compounds. NOT FOR: writing an individual asset (use suede-copy), technical or on-page SEO audits (use suede-seo-audit), or social-channel production (use suede-social).

インストール方法を見る

含まれるファイル(5)

  • SKILL.md16.7 KB
  • agents/openai.yaml558 B
  • CARD.md4.3 KB
  • evals/evals.json6.1 KB
  • references/headless-cms.md8.3 KB

SKILL.md(原文)

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

Suede Content Strategy

Use this Suede content-strategy playbook to plan evidence-backed content that earns search, sharing, trust, or qualified demand.

Before Planning

Read .agents/product-marketing.md first if it exists and ask only for what it does not cover; see suede-product-marketing for path fallbacks.

Gather this context (ask if not provided):

1. Business Context

  • What does the company do?
  • Who is the ideal customer?
  • What's the primary goal for content? (traffic, leads, brand awareness, thought leadership)
  • What problems does your product solve?

2. Customer Research

  • What questions do customers ask before buying?
  • What objections come up in sales calls?
  • What topics appear repeatedly in support tickets?
  • What language do customers use to describe their problems?

3. Current State

  • Do you have existing content? What's working?
  • What resources do you have? (writers, budget, time)
  • What content formats can you produce? (written, video, audio)

4. Competitive Landscape

  • Who are your main competitors?
  • What content gaps exist in your market?

Searchable vs Shareable

Every piece of content must be searchable, shareable, or both. Searchable is the default first priority because search demand is measurable; treat that as a starting rule, not a universal truth, and reverse it when the user's goal or evidence says otherwise (a category with no search volume, a brand-led launch). Record which order you chose and why: it feeds the weights in "Prioritizing Content Ideas."

Searchable content captures existing demand. Optimized for people actively looking for answers.

Shareable content creates demand. Spreads ideas and gets people talking.

When Writing Searchable Content

  • Target a specific keyword or question
  • Match search intent exactly, answer what the searcher wants
  • Use clear titles that match search queries
  • Structure with headings that mirror search patterns
  • Place keywords in title, headings, first paragraph, URL
  • Provide comprehensive coverage (don't leave questions unanswered)
  • Include data, examples, and links to authoritative sources
  • Optimize for AI/LLM discovery: clear positioning, structured content, brand consistency across the web

When Writing Shareable Content

  • Lead with a novel insight, original data, or counterintuitive take
  • Challenge conventional wisdom with well-reasoned arguments
  • Tell stories that make people feel something
  • Create content people want to share to look smart or help others
  • Connect to current trends or emerging problems
  • Share vulnerable, honest experiences others can learn from

Content Types

Searchable Content Types

Use-Case Content Formula: [persona] + [use-case]. Targets long-tail keywords.

  • "Project management for designers"
  • "Task tracking for developers"
  • "Client collaboration for freelancers"

Hub and Spoke Hub = comprehensive overview. Spokes = related subtopics. Create the hub first, then build spokes, and interlink them. See "Content Pillars and Topic Clusters" below for the structure and the URL guidance.

Template Libraries High-intent keywords + product adoption.

  • Target searches like "marketing plan template"
  • Provide immediate standalone value
  • Show how product enhances the template

Shareable Content Types

Thought Leadership

  • Articulate concepts everyone feels but hasn't named
  • Challenge conventional wisdom with evidence
  • Share vulnerable, honest experiences

Data-Driven Content

  • Product data analysis (anonymized insights)
  • Public data analysis (uncover patterns)
  • Original research (run experiments, share results)

Expert Roundups A selected set of relevant, verified experts answering one specific question. Distribution depends on contributor permission and actual promotion.

Case Studies Structure: Challenge → Solution → Results → Key learnings

Meta Content Behind-the-scenes transparency. "How We Got Our First $5k MRR," "Why We Chose Debt Over VC."

For programmatic content at scale, route the data and template system to suede-programmatic-seo.


Content Pillars and Topic Clusters

Content pillars are the 3-5 core topics your brand will own; each pillar spawns a cluster of related content. Most of the time all of it can live under /blog with good internal linking. Dedicated pillar pages with custom URL structures (like /guides/topic) are only needed for comprehensive resources with multiple layers of depth.

How to Identify Pillars

  1. Product-led: What problems does your product solve?
  2. Audience-led: What does your ICP need to learn?
  3. Search-led: What topics have volume in your space?
  4. Competitor-led: What are competitors ranking for?

Structure is pillar (hub) → subtopic clusters → articles, each article linking to its siblings and up to the hub. The Topic cluster map in Output Format is the shape to emit.

Pillar Criteria

Good pillars should:

  • Align with your product/service
  • Match what your audience cares about
  • Have search volume and/or social interest
  • Be broad enough for many subtopics

Keyword Research by Buyer Stage

Map topics to the buyer's journey using the modifier set for each stage:

StageModifiersTriggered by
Awareness"what is," "how to," "guide to," "introduction to"Customers asking basics
Consideration"best," "top," "vs," "alternatives," "comparison"Customers evaluating multiple tools
Decision"pricing," "reviews," "demo," "trial," "buy"Pricing coming up in sales calls
Implementation"templates," "examples," "tutorial," "how to use," "setup"Support tickets showing setup struggles

Worked example, Consideration stage for a project-management tool: "Best Project Management Tools for Remote Teams," "Asana vs Trello vs Monday," "Basecamp Alternatives." Apply the same pattern per stage using the user's own category nouns, never these ones.


Content Ideation Sources

Research Surface Check

Before external research, inspect the tools and connected sources that are currently callable and authorized in this session. Use product analytics, Search Console or keyword exports, customer material, support data, approved Drive sources, or a callable browser/search surface only when access actually exists. Record each source URL or file, owner, retrieval date, and relevant scope.

If no external research surface is available, continue with user-supplied URLs, exports, transcripts, and known first-party evidence. Otherwise return a compact manual-research list with exact queries and fields to capture. Label hypotheses and unverified competitor observations; never imply that a search was run.

1. Keyword Data

If user provides keyword exports (Ahrefs, SEMrush, GSC), analyze for:

  • Topic clusters (group related keywords)
  • Buyer stage (awareness/consideration/decision/implementation)
  • Search intent (informational, commercial, transactional)
  • Quick wins (low competition + decent volume + high relevance)
  • Content gaps (keywords competitors rank for that you don't)

Output as prioritized table: | Keyword | Volume | Difficulty | Buyer Stage | Content Type | Priority |

2. Call Transcripts

If user provides sales or customer call transcripts, extract:

  • Questions asked → FAQ content or blog posts
  • Pain points → problems in their own words
  • Objections → content to address proactively
  • Language patterns → exact phrases to use (voice of customer)
  • Competitor mentions → what they compared you to

Output content ideas with supporting quotes.

3. Survey Responses

If user provides survey data, mine for:

  • Open-ended responses (topics and language)
  • Common themes, with sample count and observed proportion recorded
  • Resource requests (what they wish existed)
  • Content preferences (formats they want)

4. Forum Research

If an authorized browser or search surface is currently callable, use it to find recent first-party community evidence. Otherwise ask for relevant URLs or provide the queries below for manual collection.

Reddit: site:reddit.com [topic]

  • Top posts in relevant subreddits
  • Questions and frustrations in comments
  • Upvoted answers (validates what resonates)

Quora: site:quora.com [topic]

  • Most-followed questions
  • Highly upvoted answers

Other: Indie Hackers, Hacker News, Product Hunt, industry Slack/Discord

For each item, capture the source URL, publication date, retrieval date, community context, and a short evidence excerpt. Distinguish engagement signals from proof of customer demand.

5. Competitor Analysis

Use a currently callable, authorized browser/search surface or user-supplied competitor URLs. If neither is available, produce a manual research checklist and do not invent page inventories, rankings, engagement, or gaps.

Find their content: site:competitor.com/blog

Analyze:

  • Observable posts and dated engagement signals
  • Topics covered repeatedly
  • Gaps they haven't covered
  • Case studies (customer problems, use cases, results)
  • Content structure (pillars, categories, formats)

Identify hypotheses to validate:

  • Topics you can cover better
  • Angles they're missing
  • Outdated content to improve on, based on a visible date or stale claim

6. Sales and Support Input

Extract from customer-facing teams:

  • Common objections
  • Repeated questions
  • Support ticket patterns
  • Success stories
  • Feature requests and underlying problems

Prioritizing Content Ideas

Score each idea on four factors. The weights below are an illustrative starting point, not a universal truth; change them to match the user's business goal and record the chosen decision rule.

1. Customer Impact (40%)

  • How frequently did this topic come up in research?
  • What percentage of customers face this challenge?
  • How emotionally charged was this pain point?
  • What's the potential LTV of customers with this need?

2. Content-Market Fit (30%)

  • Does this align with problems your product solves?
  • Can you offer unique insights from customer research?
  • Do you have customer stories to support this?
  • Will this naturally lead to product interest?

3. Search Potential (20%)

  • What's the monthly search volume?
  • How competitive is this topic?
  • Are there related long-tail opportunities?
  • Is search interest growing or declining?

4. Resource Requirements (10%)

  • Do you have expertise to create authoritative content?
  • What additional research is needed?
  • What assets (graphics, data, examples) will you need?

Scoring Template

IdeaCustomer Impact (40%)Content-Market Fit (30%)Search Potential (20%)Resources (10%)Total
Topic A89768.0
Topic B67987.1

Refreshes and Stop-Doing Decisions

A portfolio compounds only if something leaves it. Every strategy must name what stops, not just what starts. Audit existing assets against dated evidence, traffic, conversions, rankings, and last-updated date, and assign each one of four outcomes:

OutcomeWhenWhat it means
KeepStill ranking or converting against its goal, and the claims are currentNo action; next audit at the normal cadence
RefreshThe topic still matters and the URL still has authority, but the piece has decayed: stale data, dated claims, or a slipping positionRewrite in place, keep the URL, record the new last-updated date
ConsolidateTwo or more pieces target the same intent and split their own signalMerge into the strongest URL, redirect the others, fold the unique sections in
KillThe topic no longer serves a pillar, or two consecutive review windows show no traffic, no conversions, and no strategic usePropose removal or de-indexing, and stop there, because Boundaries forbids executing it

Decision rule, in order: duplicated intent → Consolidate; else topic still maps to a live pillar → Refresh; else → Kill. Never refresh a piece whose pillar was retired: that is sunk cost wearing an editorial hat. Every row names the evidence that triggered it (metric, window, source) and the accountable owner; recommending is the whole job, since publishing, deleting, redirecting, and de-indexing all need explicit authorization.

Hand the recurring cadence that keeps this audit running, decay watch, ranking-drop watch, refresh queue, to suede-marketing-loops. This skill decides what gets refreshed or killed; that one decides how often the check runs.


Reject these defaults

The generic content strategy writes itself, which is exactly the problem. Do not ship:

  • Pillars that are category nouns: "Productivity," "Marketing," "Growth." A pillar is a claim the brand can own, in the customer's words.
  • A cluster map that is the pillar list re-indented. If every spoke is the pillar name plus a modifier, no clustering happened.
  • "The Ultimate Guide to X," "Everything You Need to Know About X," "X 101": titles that could sit on any competitor's blog.
  • "10 Best Tools for Y" with the user's product at #1. That is not a comparison.
  • A cadence with no owner. "Publish 2x/week" with nobody named is a wish.
  • Topics sourced from the model's general knowledge rather than the research surfaces above. If none was callable, say so and label the ideas hypotheses.

Output Format

Emit the strategy in exactly this shape:

## Content pillars
| Pillar | The claim it owns | Evidence it matters to the ICP | Product connection |
|---|---|---|---|
| [pillar] | [one sentence] | [source + date] | [what it sells] |

## Priority topics
### [Topic title]
- **Type:** searchable / shareable / both: [use-case, hub-and-spoke, thought
  leadership, data-driven, case study, meta]
- **Target query + buyer stage:** [query]: [awareness / consideration /
  decision / implementation]
- **Why this topic:** [the customer-research evidence, with its source and date]
- **Score and owner:** [Impact / Fit / Search / Resources] = [total]; [owner,
  rough effort]

## Topic cluster map
[Pillar]
├── [Cluster]
│   ├── [Article] → links to [Article]
│   └── [Article]
└── [Cluster]
    └── [Article]

## Stop-doing
| Existing asset | Outcome | Evidence | Owner |
|---|---|---|---|
| [URL] | Keep / Refresh / Consolidate / Kill | [metric, window, source] | [who] |

## Open questions
[What could not be evidenced, and what would settle it]

Task-Specific Questions

  1. What patterns emerge from your last 10 customer conversations?
  2. What questions keep coming up in sales calls?
  3. Where are competitors' content efforts falling short?
  4. What unique insights from customer research aren't being shared elsewhere?
  5. Which existing content drives the most conversions, and why?

References

  • Headless CMS Guide: CMS selection, content modeling for marketing, editorial workflows, platform comparison (Sanity, Contentful, Strapi)

Boundaries

  • Do not claim demand, authority, rank potential, or audience fit without naming the current evidence and decision criterion.
  • Do not publish, delete, redirect, deindex, or change an editorial calendar or CMS without explicit authorization.
  • Do not invent expertise, customer proof, keyword data, or citations to fill a content gap.
  • Do not decide legal, rights, or brand-claim questions; flag them for the accountable owner before publication.

Routing

  • Need an individual asset written -> use suede-copy.
  • Need technical or on-page organic diagnosis -> use suede-seo-audit.
  • Need scaled page systems -> use suede-programmatic-seo.
  • Need email or social production -> use suede-emails or suede-social.
  • Need the pipeline staffed as roles with contracts, a handoff record, and one distinct argument per distributed asset -> use suede-newsroom. A weekly founder interview or voice note that feeds separate founder and company account lanes uses that skill's founder-led mode.
  • Need the refresh, decay, or ranking-drop audit to run on a cadence -> use suede-marketing-loops.
  • Need the behavioral mechanism behind a title, hook, or CTA, stated as a testable hypothesis -> use suede-marketing-psychology.
  • From those skills, route portfolio priorities, pillars, clusters, and cadence back to suede-content-strategy.

レビュー

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

同じリポジトリのスキル

概要と使いどころ

Suede-affiliated Amazon money-recovery audit for restocking fees, short or denied refunds, and Amazon-billed subscriptions. Use when the user mentions a restocking fee, a short or denied Amazon refund, or a forgotten Prime Video Channel, Audible, Kindle Unlimited, or Prime charge, or asks whether Amazon still owes or bills them. Read-only discovery; no chat, cancellation, or dispute without the account owner's per-item confirmation, and never a promise of recovery. Requires an authenticated Claude in Chrome session. NOT FOR: bank chargebacks, marketplace A-to-z seller claims, price-protection claims, or subscriptions billed outside Amazon (use subscription-recovery).

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

JasonColapietro/suede-creator-skills1272026年10月12日 更新

Suede Labs Android app factory: plan, build, test, and release a production-grade native Android app from a product idea through Google Play. Use for requests to create, ship, submit, monetize, or modernize an Android app. Covers Kotlin and Jetpack Compose architecture, API-level policy verification, accessibility, privacy and Data Safety, Play Billing, Play Integrity, account deletion, testing, performance, store assets, signing, staged rollout, and a release evidence gate. NOT FOR: iOS work (private Suede Labs companion, not in this pack: ios-app-factory), a review-only pass on an existing app (use suede-code-review), or live Play listing and keyword audits on a shipped app (use suede-aso).

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

JasonColapietro/suede-creator-skills1272026年10月12日 更新

Design, review, and visually QA web and app interfaces against explicit design laws so shipped screens look intentional instead of generic AI output.

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

JasonColapietro/suede-creator-skills1272026年10月12日 更新

Suede AI full-stack surface builder that runs design, copy, and visual QA as one pass: landing pages, brand surfaces, product UI, dashboards, campaigns, launch pages, and reference-to-target restyles (suedify). Use when a build needs layout and words together, when a redesign or launch surface has to ship end to end, when the request is 'make this site look like that one', or when design, copy, asset, and QA lanes have to move at once. NOT FOR: a design-token, dark-mode, or single-component decision (use suede-design); copy with no layout work (use johnny-suede-write, or suede-copy for one standalone conversion surface); conversion and funnel architecture (use suede-site-alchemy); multi-agent orchestration protocols, WIP protection, and rollback trees (use suede-agent-teams).

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

JasonColapietro/suede-creator-skills1272026年10月12日 更新

Suede Labs full writing stack: sharper copy for docs, pages, email, social, headlines, CTAs, product listings, and public explainers, with an SEO/AEO/AI EO pass, persona and framework selection, brand-voice alignment, and a scored ship gate. Use when a writing job spans more than one surface, needs a voice retune as well as a draft, needs discoverability metadata alongside the copy, when the document is one an agent reads such as a SKILL.md, CLAUDE.md, or AGENTS.md, or when the user asks for 'the full writing stack', a launch package, or a public explainer talk-track. NOT FOR: one standalone conversion surface in one pass (use suede-copy); stripping AI patterns from text you did not write (use suede-deslop); a researched multi-phase piece for a high-stakes public surface (use suede-ship-copy); a deep standalone SEO audit (use suede-seo-audit); copy that ships inside a design or layout build (use johnny-suede-design).

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

JasonColapietro/suede-creator-skills1272026年10月12日 更新

Suede Labs workflow for turning a website, PWA, dashboard, or marketplace into an iOS app. Use when the user has a live site or web app and asks to put it on the App Store, wrap it in an app, ship an iOS version, or convert a PWA to native, covers URL audit, shell-vs-native strategy, App Store 4.2 wrapper risk, native value requirements, screenshots, metadata, privacy answers, and the release gate. NOT FOR: building a native iOS app with no existing site (private Suede Labs companion, not in this pack: ios-swiftui-product); repairing or releasing an existing Capacitor shell (private Suede Labs companion, not in this pack: ios-capacitor-shell); Android conversions (use android-app-factory); live listing and keyword audits on a shipped app (use suede-aso).

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

JasonColapietro/suede-creator-skills1272026年10月12日 更新

JasonColapietro のスキルをすべて見る

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