Agent Skills: content-strategy
World-class content strategy expertise combining the frameworks of Andy Crestodina's data-driven approach, Ann Handley's "everybody writes" philosophy, and the content engines that power companies like HubSpot, Ahrefs, and Intercom. Content strategy isn't about creating content - it's about creating the right content for the right audience at the right time in the right format. The best content strategists think in systems, not pieces. They build content engines that compound over time and turn strangers into customers and customers into advocates. Use when "content strategy, content plan, editorial calendar, blog strategy, content marketing, topic clusters, pillar content, content audit, content calendar, SEO content, content distribution, content funnel, thought leadership, content engine, content topics, what to write, content, strategy, editorial, SEO, blog, planning, distribution, measurement" mentioned.
Install this agent skill to your local
Skill Files
The files that make up content-strategy.
Loading file tree…
More agent skills
- browser-toolsInteractive browser automation via Chrome DevTools Protocol. Use when you need to interact with web pages, test frontends, or when user interaction with a visible browser is required.
- apollo-reference-architecture'Implement Apollo.io reference architecture.
- understand-prGuided interactive PR review — understand the history and context before forming opinions
- aspire-service-defaultsCreate a shared ServiceDefaults project for Aspire applications. Centralizes OpenTelemetry, health checks, resilience, and service discovery configuration across all services.
- architecture-decision-recordsComprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the context and rationale behind significant technical decisions.
- property-based-testingWrites, reviews, and debugs property-based tests — Hypothesis, fast-check, proptest, jqwik, rapid, and Echidna or Medusa for Solidity invariants. Use whenever tests should cover a whole input domain instead of a hand-picked list of examples: encode/decode and serialize/deserialize pairs, parsers, canonicalizers and normalizers, validators, numeric and Decimal types, comparators and sort order, data structures, and smart-contract state invariants. Also use when adding cases to an existing @given, fast-check, or proptest suite, when judging whether existing property tests assert anything real, and when a generator has shrunk a counterexample and you need to tell a wrong property from a genuine bug. Not for coverage-guided binary fuzzing (libFuzzer, AFL), mutation-testing campaigns, static analysis, benchmarking, or end-to-end UI tests.