From alemtuzlak-skills
Use when the user wants to run multiple marketing skills together (brief, blog post, social copy, changelog, newsletter, video script) from a single input, or when they mention "marketing pipeline", "full marketing", or "launch content"
npx claudepluginhub alemtuzlak/skills --plugin alemtuzlak-skillsThis skill uses the workspace's default tool permissions.
Orchestrate any combination of `/marketing-brief`, `/changelog`, `/blog-post`, `/newsletter`, `/social-copy`, and `/video-script` from a single input. Pick which skills to run and in what order. Each skill's output feeds into the next.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Analyzes competition with Porter's Five Forces, Blue Ocean Strategy, and positioning maps to identify differentiation opportunities and market positioning for startups and pitches.
Share bugs, ideas, or general feedback.
Orchestrate any combination of /marketing-brief, /changelog, /blog-post, /newsletter, /social-copy, and /video-script from a single input. Pick which skills to run and in what order. Each skill's output feeds into the next.
This skill does NOT duplicate the logic of the sub-skills. It collects input, asks which skills to run, then invokes them in sequence, passing each output as input to the next. Each skill runs its full process including its own discovery, configuration, writing, and output phases.
Accept the same input types as the sub-skills:
#number)v1.0...v2.0)If no argument provided, ask: "What should I create marketing content for? You can provide a PR, git ref range, file path, or just describe the feature."
Ask the user which skills to run:
"Which of these do you want me to generate?"
- Marketing brief (
/marketing-brief)- Changelog (
/changelog)- Blog post (
/blog-post)- Remotion video (
/remotion-video)- Newsletter (
/newsletter)- Social copy (
/social-copy)- Video script (
/video-script)"Pick any combination (e.g. '1, 3, and 5', 'all', '3 only')."
(Menu numbering is for selection only; execution follows the chain in Step 3.)
"all" means skills 1 through 7.
After selection, check if the original input is compatible with each selected skill:
Ask where to save all generated content:
"Want all content saved to a single directory? (e.g.
marketing/launch-<feature>/). Otherwise each skill will use its own default location."
If the user picks a single directory, all files go into that directory:
brief.md (marketing brief)changelog.md (changelog)blog-post.md (blog post)video.mp4 + poster.jpg + remotion/ subdirectory (remotion video)newsletter.md (newsletter)social-copy.md (social copy)video-script.md (video script)Create the directory if it doesn't exist. When each sub-skill asks "where to save?", respond with the shared path and filename on behalf of the user.
If the user declines, let each sub-skill use its own default path. Track the actual output paths for the summary.
Run selected skills in this order (each output feeds the next):
changelog -> marketing-brief -> blog-post -> remotion-video -> newsletter -> social-copy -> video-script
The order is designed so that upstream outputs enrich downstream skills:
video.mp4 + poster.jpg paths so the posts can embed them.If a skill in the chain is not selected, skip it. The next skill receives whatever the most recent upstream output was. If no upstream skill was selected, use the original input.
When feeding output from one skill to a non-adjacent skill (e.g. changelog directly to social-copy), explicitly tell the downstream skill what the input represents: "This is a changelog. Treat it as a structured list of feature descriptions and changes."
For each selected skill, invoke it using the Skill tool:
Between skills, confirm with the user before proceeding:
"[Skill] is done. Ready to move on to [next skill]?"
This gives the user a chance to adjust, take a break, or stop early.
If a sub-skill fails or the user cancels mid-process, ask: "Want to skip this skill and continue to the next one, or stop the pipeline here?" List what was already completed.
After all selected skills are complete, present a summary:
"Here's everything that was generated:"
- Changelog:
<path>/changelog.md- Marketing brief:
<path>/brief.md- Blog post:
<path>/blog-post.md- Remotion video:
<path>/video.mp4+<path>/poster.jpg(+<path>/remotion/project if kept)- Newsletter:
<path>/newsletter.md- Social copy:
<path>/social-copy.md- Video script:
<path>/video-script.md(Only list the skills that were actually run. Show actual paths used.)