CRAFT Content report
Content Repurposer: your result
This answer uses a made-up example company. Change the details above and press Run to see your own result.
Content Repurposer
For content and demand gen teams. The decision: how do we get more from one piece of content?
Give it a piece of content and its type, and get key points, a LinkedIn post, an X thread, an email, a blog summary, quote cards and a distribution plan.
Paste your source content (blog post, webinar transcript, podcast transcript, white paper, case study, research report, or presentation) into Content Repurposer with your brand voice and core message. The tool extracts key points as whole sentences in source order (shortening sentences over 260 characters at a clause boundary for social posts), checks for a labelled proof line starting with Proof: or Results:, and drafts the default five formats (LinkedIn Post, Twitter/X Thread, Email Version, Blog Summary, and Quote Cards) or optional formats (infographic outline, video script, podcast talking points, slide deck outline, and newsletter section).
This sample is a made up example, built from the inputs behind Fill in an example. It shows part of one section of the answer.
Measure tickets resolved, not tickets deflected.
Most support automation fails because it only drafts replies.
The tickets that cost the most need an action: a refund, a reorder, an address change.
What is your view?
#AINative
See the full example answer or run it with your own details.
CRAFT Content report
This answer uses a made-up example company. Change the details above and press Run to see your own result.
When a tool is not enough: if the decision needs more than one answer, talk it through in a call. Book 45 minutes with Shashwat.
What next? Work with Shashwat Try another tool See all 85 tools and skills
Generated on 2 November 2026 from this branch, with the inputs behind Fill in an example. Your own inputs give a different result.
CRAFT Content report
Not given: a proof line. The source has no line that starts "Proof:" or "Results:", so no piece carries a customer result; add one customer result with its figure to the source to make the pieces stronger.
Draft only. Before you use it: confirm the source URL for the "Read the full blog post" line of the email and the last tweet before sending and confirm the sender name before the email can be sent. Supply confirmed Reader action, Source URL and Sender as labelled lines in the source notes.
Measure tickets resolved, not tickets deflected.
Most support automation fails because it only drafts replies.
The tickets that cost the most need an action: a refund, a reorder, an address change.
What is your view?
#AINative
Tweet 1 (Hook):
Measure tickets resolved, not tickets deflected. A thread.
Tweet 2:
1/ Most support automation fails because it only drafts replies.
Tweet 3:
2/ The tickets that cost the most need an action: a refund, a reorder, an address change.
Tweet 4:
3/ What is your view?
Subject: Measure tickets resolved, not tickets deflected
Hello,
Most support automation fails because it only drafts replies.
The tickets that cost the most need an action: a refund, a reorder, an address change.
Confirm the reader action before sending.
Source link: unknown; confirm before sending.
Best regards,
Sender: unknown; confirm before sending.
Other subject lines to test: What we learned: Most support automation fails because it only drafts replies
Measure tickets resolved, not tickets deflected
This is written for readers such as head of customer experience and chief technology officer, who watch automated resolution rate, accuracy on an evaluation set and escalation rate.
The bottom line: Measure tickets resolved, not tickets deflected.
Quote Card 1:
"Most support automation fails because it only drafts replies"
Quote Card 2:
"The tickets that cost the most need an action: a refund, a reorder, an address change"
Quote Card 3:
"Let the AI agent take that action inside your help desk, with a person approving anything that moves money, and measure tickets resolved, not tickets deflected"
| Attribute | Value |
|---|---|
| Source Type | blog post |
| Word Count | 51 |
| Key Points Found | 3 |
| Proof Items Found | 0 |
| Brand Voice | professional |
| Core Message | Measure tickets resolved, not tickets deflected |
| Formats | Default top 5 |
Chosen as whole sentences from your source, in its order. In the posts and tweets a sentence over 260 characters is shortened at a clause boundary; the list above and the blog summary keep the longer form.
Brand voice (professional): plain and formal greeting, sign-off and closing question; the sentences taken from your source are kept as you wrote them.
Sector: read from your inputs as AI native. Business model: not stated. Tell us how you charge and the plan will adjust.
Billing dependent steps are conditional: trials, seats and recurring renewals require a subscription; a statement of work requires a services contract; site or link commitments require connectivity billing. Confirm the applicable choice before using those steps.
When a tool is not enough: if the decision needs more than one answer, talk it through in a call. Book 45 minutes with Shashwat.
The tool splits your source text into whole sentences in their original order and formats them into a LinkedIn Post, a Twitter/X Thread, an Email Version, a Blog Summary, and Quote Cards. Sentences over 260 characters are shortened at a clause boundary for social posts, and if your input did not include a line starting with "Proof:" or "Results:", the output flags that no customer result was found and leaves proof out of the drafts. Check the Email Version placeholders (Reader action, Source link: unknown, and Sender: unknown) before sending anything.
Come back whenever you publish a new article, webinar transcript, research report, or case study and want channel drafts built strictly from the sentences in that piece. Re-run it with a "Proof:" line added whenever new customer numbers are approved. The tool applies the same fixed rules every time. It does not call an AI model, and this site does not keep what you enter.
Add CRAFT Content once (see Use it in Claude, ChatGPT or Gemini), then ask in plain words. Here is a prompt built from the tested example:
My role is not stated. Ask me for my role first. Use CRAFT Content's Content Repurposer tool. source content: Most support automation fails because it only drafts replies. The tickets that cost the most need an action: a refund, a reorder, an address change. Let the AI agent take that action inside your help desk, with a person approving anything that moves money, and measure tickets resolved, not tickets deflected; source type: Blog post; brand voice: Professional; key message: Measure tickets resolved, not tickets deflected. If this tool is unavailable, ask me to open its web page; do not invent its output. In Gemini CLI or Antigravity, use the Helix GTM Suite skills package for related guidance, without claiming to run this connector.
You do not need to sign in. A web browser is enough, and the answer comes back in a second or two.
It applies fixed rules in the CRAFT Content code to the inputs above and returns text. It does not call an AI model, does not look anything up, and does not store what you type. The web form and the AI assistant connector run the same tool code, so the same input gives the same answer in both.
MCP tool name: content_repurposer. REST: POST https://craft-content.gtmhelix.com/api/tools/content_repurposer with this JSON body (see How it works):
{
"input": {
"source_content": "Most support automation fails because it only drafts replies. The tickets that cost the most need an action: a refund, a reorder, an address change. Let the AI agent take that action inside your help desk, with a person approving anything that moves money, and measure tickets resolved, not tickets deflected.",
"source_type": "blog_post",
"brand_voice": "professional",
"key_message": "Measure tickets resolved, not tickets deflected"
}
}
Run a Helix tool in your browser, then take the result to ChatGPT, Claude or Gemini. Connectors work with supported plans in Claude, ChatGPT, Cursor, VS Code and Windsurf. The Helix GTM Suite skills package supports Claude Code, Gemini CLI, Antigravity, Cursor and VS Code, and is available through skills.sh. Each plugin has its own installation steps, below or on its own page.
Connector setup guides · Skills package setup guide · Find the skills on skills.sh