Marketing Crew Pack
Seven agents for one offer. Positioning, then a 30-day calendar, then four-block landing copy, then a ship-day checklist. Competitor watch is a side loop. Threads and changelog notes attach when an article or a commit range exists. It does not post.
Works with any agent that signs in to Agensi, such as Claude, ChatGPT, Claude Code, Cursor and Codex CLI.
One payment, lifetime access. 7 skills unlock instantly in your library.
What's included
7 skillsExtracts one ICP, one enemy, one promise, and one proof point to create a fluff-free positioning contract.
Generates a constrained 30-day marketing calendar from a single product thesis and platform limits.
Generates a high-conversion, four-block landing page draft stripped of marketing fluff and grounded in product data.
Generates a complete ship-day marketing checklist including store listings, pixel notes, emails, and support replies.
Extracts material, primary-source news for a specific watchlist into a structured markdown digest.
Transforms technical articles into structured X threads and LinkedIn posts without marketing fluff or handle leaks.
Extracts human-readable changelogs and launch notes from git commits while filtering out technical noise and fluff.
See it in action
Ideal Customer Profile (ICP) Positioning
Example session with this skill installed
Run positioning for "TaskFlow". Brief is at docs/brief.md. Proof: "Used by 12 teams at Acme Corp to reduce sprint planning from 4 hours to 45 minutes." Category: Task management.
- Read your context and instructions
- Compiled the ideal customer profile
I have processed the positioning for TaskFlow. I interrogated the brief, removed three instances of "seamless" and "intuitive," and mapped the messaging to your Acme Corp proof point.
Positioning Contract: TaskFlow
Header
- Product: TaskFlow
- Category: Task management
- Status: READY
ICP
- Title: Engineering Lead
Context: Managing 2-3 cross-functional squads using Jira but relying on manual spreadsheets for capacity planning.
- Job to be Done: Allocate developer resources without overbooking during mid-sprint changes.
- Buying Trigger: A sprint fails because a sub-task was hidden in a deep backlog view.
- Not: Individual contributors or C-suite executives.
Enemy
- The "Capacity Spreadsheet." It fails because it requires manual updates and is always 24 hours behind the actual ticket status.
Promise
- Engineering Leads can reallocate sprint capacity in under five minutes when a high-priority bug breaks the sprint.
Proof
- Used by 12 teams at Acme Corp to reduce sprint planning from 4 hours to 45 minutes.
One-Liner
- TaskFlow lets Engineering Leads reallocate sprint capacity in under five minutes.
Killed Soup
| Fuzzy Word | Replacement / Action |
|---|---|
| seamless | dropped: no proof |
| intuitive | Replaced with "under five minutes" |
| robust | Replaced with "12 teams at Acme Corp" |
Next steps
- Review the
docs/positioning.mdfile for accuracy. - Use this file as the input for the
landing-copyorlaunch-checklistskills. - Address the open question regarding the secondary "Project Manager" persona in the parking lot.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads these skills and uses them on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every skill in this bundle goes through our trust checks.
Security scanned
Checked by our 8-point scan before listing
1 use
Times these skills were used to date
Money-back guarantee
Doesn't do what its page promises? You get your money back.