From hive
Content planning and editorial strategy for a technical B2B audience. Use when building content calendars, selecting blog topics, planning case studies, mapping content pillars, or creating a publishing roadmap. Triggers on "content calendar", "blog strategy", "what should we write about", "content pillars", "editorial calendar", "content plan", "SEO topics".
npx claudepluginhub skywalking-dev/hiveThis skill uses the workspace's default tool permissions.
Skywalking creates content to build authority in LATAM tech, attract clients who value craft, and convert readers who have real engineering problems to solve.
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Skywalking creates content to build authority in LATAM tech, attract clients who value craft, and convert readers who have real engineering problems to solve.
Every piece either builds SEO equity, builds reputation, or both. Nothing else justifies the effort.
Good topics satisfy at least 2 of 3:
ES-LATAM topics: lower competition, same audience in LATAM, compounds faster than EN.
| Week | Title | Pillar | Format | Channel | CTA | Owner |
|---|---|---|---|---|---|---|
| W1 | [topic] | [pillar] | Blog/Case study/Tutorial | Blog + LinkedIn | [action] | [who] |
Plan 4 weeks ahead minimum. One case study per month if client work permits.
Blog post (1500-2500 words)
→ 3 LinkedIn posts
→ 1 email newsletter
→ 1 WhatsApp broadcast (opt-in)
→ X thread
Never repost same text across channels. Adapt to platform norms.
Blog posts: Problem → context → solution → result → CTA. Min 1 code block per post.
Case studies: Client problem → what we built → measurable result → quote. Real numbers or don't publish.
Tutorials: Working code. Tested. Explain the why. Link to repo.
## Content Plan: [Quarter/Campaign]
**Goal:** [metric + target]
**Audience:** [who]
**Cadence:** [posts/week]
**Pillars:** [which + angle]
**Topic backlog (prioritized):**
1. [title] — [pillar] — [format] — [search intent]
**Editorial calendar:** [table]
**Repurposing plan:** [what becomes what]
**Success metrics:** [baseline → target]