content-growth-studio

Route inputs to specialized sub-skills and assemble channel-ready content packages.

Updated Mar 3, 2026
One-click install
npx skills add https://github.com/TimLai666/skills --skill content-growth-studio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: content-growth-studio
Source: https://github.com/TimLai666/skills/tree/main/content-growth-studio
Command: npx skills add https://github.com/TimLai666/skills --skill content-growth-studio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the end-to-end planning, analysis, packaging, and orchestration of growth-oriented content across article, video, and social channels, reducing handoff friction and ensuring channel-appropriate outputs.

Core Features & Use Cases

  • Decision-tree workflow to determine entry_path and mode (source-led vs brief-led).
  • Channel framing and packaging that adapts to article, long-form video, short-form video, or social assets.
  • Integrated workflow design, SOPs, and batch-production planning for repeatable content production.

Quick Start

Provide source artifacts or a brief, then I will detect entry path and mode and deliver a channel-ready content package.

Frequently Asked Questions about content-growth-studio

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I package growth content for different channels like articles and videos?

Source-led growth content creation begins by providing URLs, transcripts, or notes, which the system detects and routes into a specialized workflow to extract insights and frame channel-ready outputs.

How do I plan content production from a brief instead of a source?

Yes, batch-production planning is supported through integrated workflow design and SOPs, enabling repeatable content orchestration across article, video, and social formats with scope control and safety checks.

What is the difference between source-led and brief-led content workflows?

Source-led workflows process existing URLs and transcripts to extract and repackage insights, while brief-led workflows use submitted briefs to guide original content generation and channel framing from the start.

Does this workflow require specific input formats to start routing content?

The workflow accepts URLs, transcripts, briefs, and notes as input formats, automatically detecting the entry path and mode to determine routing and apply the appropriate channel packaging rules.