New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Suede Content Strategy

by JasonColapietro in JasonColapietro/suede-creator-skills

Suede-owned content-strategy discipline for audience questions, content pillars, topic clusters, editorial priorities, cadence, distribution, refreshes, and stop-doing decisions.

MITAuto-check passedWriting & Content

Install Suede Content Strategy

skills CLI
$ npx skills add JasonColapietro/suede-creator-skills --skill suede-content-strategy -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install JasonColapietro/suede-creator-skills suede-content-strategy --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/JasonColapietro/suede-creator-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/suede-content-strategy .claude/skills/suede-content-strategy && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
suede-content-strategy
GitHub stars
127
Token cost
~4.3k tokens
SKILL.md length
2,096 words
Files
5 (incl. references)
Skills in repo
78
Repo updated
First seen
Licence
MIT

At a glance

Suede-owned content-strategy discipline for audience questions, content pillars, topic clusters, editorial priorities, cadence, distribution, refreshes, and stop-doing decisions.

  • Works in 12 steps: Business Context → Customer Research → Current State → …
  • Deciding what to publish
  • SKILL.md covers Before Planning, Searchable vs Shareable, Content Types and Content Pillars and Topic…, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Suede Content Strategy is an agent skill from JasonColapietro/suede-creator-skills. 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).

Its SKILL.md is about 4.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `CARD.md`, `agents/openai.yaml` and `evals/evals.json`).

It sits in Writing & Content, covering Content strategy. The repository describes itself as: Open-source AI skills for SEO, AI search visibility, conversion copy, marketing strategy, and business operations. Reusable workflows for Claude Code and Codex, plus code review… The licence is MIT.

When your agent uses it

  • Deciding what to publish
  • Why it deserves resources
  • How the portfolio compounds

Example prompts

  • “/suede-content-strategy”

Workflow steps

12 steps, taken from the step headings in SKILL.md.

  1. Business Context
  2. Customer Research
  3. Current State
  4. Competitive Landscape
  5. Keyword Data
  6. Call Transcripts
  7. Survey Responses
  8. Forum Research
  9. Competitor Analysis
  10. Sales and Support Input
  11. Customer Impact (40%)
  12. Content-Market Fit (30%)

What it can do on your machine

Read from SKILL.md and the folder at commit e5f94d7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Suede Content Strategy loads about 4.3k tokens when it runs, and up to ~6.4k if it reads all its reference files. Until then it costs about 114 tokens; SKILL.md has 2,096 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~114
When it runs · the whole SKILL.md, loaded when a task matches
~4.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~6.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from JasonColapietro/suede-creator-skills at commit e5f94d7, republished under its MIT licence (© JasonColapietro). 2,096 words, ~4,254 tokens.

Download SKILL.mdSave it as .claude/skills/suede-content-strategy/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
suede-content-strategy
description
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).
metadata.version
2.0.0

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
Show full SKILL.md (837 more words)Show less

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.

© JasonColapietro, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (references) in skills/suede-content-strategy of JasonColapietro/suede-creator-skills.

  • SKILL.md
  • CARD.md
  • agents/openai.yaml
  • evals/evals.json
  • references/headless-cms.md

Open the folder on GitHubat commit e5f94d7

Compare with similar skills

Suede Content Strategy next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Suede Content Strategy compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Suede Content Strategy this skillJasonColapietro/suede-creator-skills127—~4.3kAutomated safety check: PassMIT
Email PlanAgriciDaniel/claude-email130—~4.3kAutomated safety check: PassMIT
Geo Review HTMLViryaZheng/recomby-geo458—~1.3kAutomated safety check: PassMIT
Content BriefMadAppGang/claude-code2851 repos~959Automated safety check: PassMIT
Gbp Postsgarrettjsmith/localseoskills121—~1.6kAutomated safety check: PassMIT
Wb Xhs Schedule Reviewwenziai/wenzi-xhs-agent-skills168—~816Automated safety check: PassNone

Similar skills

  • Email Plan

    AgriciDaniel/claude-email

    Generate comprehensive email marketing strategy with 90-day implementation roadmap.

    130 GitHub stars~4.3k tokensUpdated 4 mo ago
    Writing & ContentAuto-check passed

  • Geo Review HTML

    ViryaZheng/recomby-geo

    Render an interactive, self-contained HTML companion for a GEO content brief (04-content-brief) or a publish-ready draft (05-production), so a NON-technical client reviewer (founder, organizer…

    458 GitHub stars~1.3k tokensUpdated 3 mo ago
    Writing & ContentAuto-check passed

  • Content Brief

    MadAppGang/claude-code

    Content brief template and creation methodology for SEO-optimized content.

    285 GitHub starsUsed in 1 repo~959 tokens
    Writing & ContentAuto-check passed

  • Gbp Posts

    garrettjsmith/localseoskills

    When the user wants to create, schedule, or optimize Google Business Profile posts.

    121 GitHub stars~1.6k tokensUpdated 1 mo ago
    Writing & ContentAuto-check passed

  • Wb Xhs Schedule Review

    wenziai/wenzi-xhs-agent-skills

    A skill your agent uses when the user wants a Xiaohongshu posting calendar, weekly review board, first-10-post launch plan, 10-20-post positioning test, or data-based next-step plan.

    168 GitHub stars~816 tokensUpdated 11 days ago
    Writing & ContentAuto-check passed

  • Content

    notque/vexjoy-agent

    Content operations: editorial calendar, marketing, publishing, social media management.

    441 GitHub stars~2.9k tokensUpdated today
    Writing & ContentAuto-check: notes

More from JasonColapietro/suede-creator-skills

All 78 skills in this repo

  • Suede Release Linter

    JasonColapietro/suede-creator-skills

    Lints a local music or media release folder and scores its readiness, flagging missing files, weak metadata, artwork and stem problems, split gaps and rights blockers.

    127 GitHub stars~2.3k tokensUpdated yesterday
    Auto-check: notes

  • Creator Rights Passport

    JasonColapietro/suede-creator-skills

    Turns messy creator materials into an offline rights-and-provenance transfer package: hashed asset inventory, intake manifest, credits, license notes and a missing-information report.

    127 GitHub stars~3.7k tokensUpdated yesterday
    Auto-check: notes

  • Suede Clip to Guide

    JasonColapietro/suede-creator-skills

    Turns a video clip, interview moment or transcript into a package that bridges viewers to a long-form guide, with rights, claim and approval gates along the way.

    127 GitHub stars~4.1k tokensUpdated yesterday
    Auto-check passed

  • Suede MCP Release QA

    JasonColapietro/suede-creator-skills

    Checks a Suede AI MCP server release against a live process: the full JSON-RPC lifecycle, schemas, annotations, malformed input, catalog agreement and install docs.

    127 GitHub stars~2.1k tokensUpdated yesterday
    Auto-check passed

  • Android App Factory

    JasonColapietro/suede-creator-skills

    Takes a native Android app from product idea to Google Play release, covering Compose architecture, policy checks, privacy, billing, testing, signing and rollout.

    127 GitHub stars~2.6k tokensUpdated yesterday
    Auto-check passed

  • Suede Ad Creative

    JasonColapietro/suede-creator-skills

    Suede-owned paid-media creative system for hooks, headlines, primary text, static and motion concepts, platform specs, review pages, and test-ready variant batches.

    127 GitHub stars~5k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Suede Content Strategy

What does Suede Content Strategy do?

Suede-owned content-strategy discipline for audience questions, content pillars, topic clusters, editorial priorities, cadence, distribution, refreshes, and stop-doing decisions. Suede Content Strategy is an agent skill from JasonColapietro/suede-creator-skills. Suede-owned content-strategy discipline for audience questions, content pillars, topic clusters, editorial priorities, cadence, distribution, refreshes, and stop-doing decisions.

When should I use Suede Content Strategy?

Suede Content Strategy fits situations like: deciding what to publish; why it deserves resources; how the portfolio compounds.

How do I install Suede Content Strategy in Claude Code?

Run `npx skills add JasonColapietro/suede-creator-skills --skill suede-content-strategy -a claude-code`. Or copy the skill folder (skills/suede-content-strategy in JasonColapietro/suede-creator-skills) into .claude/skills/suede-content-strategy in your project. Claude Code loads it when a task matches its description.

How do I install Suede Content Strategy in Codex?

Run `npx skills add JasonColapietro/suede-creator-skills --skill suede-content-strategy -a codex`. Or copy the skill folder (skills/suede-content-strategy in JasonColapietro/suede-creator-skills) into .agents/skills/suede-content-strategy in your project. Codex loads it when a task matches its description.

Can I use Suede Content Strategy in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add JasonColapietro/suede-creator-skills --skill suede-content-strategy -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/suede-content-strategy, .gemini/skills/suede-content-strategy, .github/skills/suede-content-strategy and .opencode/skills/suede-content-strategy in your project.

What does Suede Content Strategy need to run?

SKILL.md names no scripts, command-line tools or credentials: Suede Content Strategy is instructions for the agent only.

Does Suede Content Strategy access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Suede Content Strategy safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Suede Content Strategy use?

Suede Content Strategy is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Suede Content Strategy use?

About 4.3k tokens (SKILL.md is roughly 17k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.1k tokens, read only when the agent opens those files.

What are the alternatives to Suede Content Strategy?

Skills that share tags, products or a category with Suede Content Strategy: Email Plan (AgriciDaniel/claude-email, 130 stars), Geo Review HTML (ViryaZheng/recomby-geo, 458 stars), Content Brief (MadAppGang/claude-code, 285 stars) and Gbp Posts (garrettjsmith/localseoskills, 121 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Suede Content Strategy?

JasonColapietro (a GitHub user) maintains it in JasonColapietro/suede-creator-skills, which has 127 GitHub stars. The repository holds 78 skills in this directory. The repository was last updated on October 10, 2026.

Source: JasonColapietro/suede-creator-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.