[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AF03NBPHKCMZXNS80THWVS":3,"skill-same:01M7AF03NBPHKCMZXNS80THWVS":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7AF03NBPHKCMZXNS80THWVS","content-draft-skill",null,"Generate first drafts across content types — blog posts, social media, emails, landing pages, press releases, case studies — with channel best practices baked in. Use when writing marketing content, creating first drafts for review, or adapting content across channels. Trigger with \"draft a blog post about\", \"write social copy for\", \"landing page for [product]\".","innFactory-AI\u002Fcompany-ai-stack-skills","innFactory-AI","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F165681221?v=4","01M7AEC27VD0D1QX2XBX441MDW","innFactory AI","01M7AEC28G25HQ9H9SN58MNV27",0,"MIT","https:\u002F\u002Fgithub.com\u002FinnFactory-AI\u002Fcompany-ai-stack-skills\u002Fblob\u002Fmain\u002Fen\u002Fskills\u002Fmarketing\u002Fcontent-draft-skill\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: content-draft-skill\ndescription: Generate first drafts across content types — blog posts, social media, emails, landing pages, press releases, case studies — with channel best practices baked in. Use when writing marketing content, creating first drafts for review, or adapting content across channels. Trigger with \"draft a blog post about\", \"write social copy for\", \"landing page for [product]\".\n---\n\n# Content Draft Skill\n\nGenerate first-draft marketing content across six content types. Each type follows channel-specific best practices for structure, length, and tone. Output is always a working first draft ready for human review and refinement — not a final publish-ready piece.\n\n## Where the Data Comes From\n\n| Source | What It Adds |\n| --- | --- |\n| **CMS via MCP** | Existing content for tone matching and internal linking |\n| **Brand guidelines via companyRAG \u002F file upload** | Voice, tone, terminology, visual style rules |\n| **Analytics via MCP** | Top-performing content patterns for the audience |\n\n> **No connected source?** Provide the data in chat or upload the relevant files — the skill works the same way.\n\n---\n\n## Workflow\n\n### Step 1: Gather Brief\n\nBefore drafting, clarify:\n\n1. Content type — blog post, social media, email, landing page, press release, or case study\n2. Topic or subject — what is this about?\n3. Target audience — who reads this? (persona, job role, stage in funnel)\n4. Goal — what should the reader do or feel after reading? (awareness, click, sign up, share)\n5. Key messages — 1-3 points that must be communicated\n6. Tone — formal, conversational, playful, authoritative? (load brand guidelines if available)\n7. Constraints — word count, required CTAs, SEO keywords, compliance disclaimers\n\nProceed with partial answers. Note assumptions.\n\n### Step 2: Route by Content Type\n\nEach content type has different structural requirements:\n\n**Blog Post**\n\n- Length: 800-2000 words depending on depth\n- Structure: Hook → Context → Main argument (with subheadings) → Takeaway → CTA\n- Include: H2\u002FH3 hierarchy, scannable paragraphs (3-4 sentences max), one CTA\n- SEO: Target keyword in title, H1, first 100 words, meta description\n- Tone: Match the publication's voice; default to informative and approachable\n\n**Social Media**\n\n- Produce variants for each platform requested:   - LinkedIn: 150-300 words, professional, hook in first line, 3-5 hashtags   - X\u002FTwitter: Under 280 characters, punchy, optional thread format for longer content   - Instagram: Caption 125-200 words, visual hook, relevant hashtags (10-15)\n- Structure: Hook line → Value → CTA\n- Include: 2-3 variants per platform with different angles\n\n**Email**\n\n- Length: 150-400 words body text\n- Structure: Subject line (3-5 variants) → Preview text → Opening hook → Body → CTA → P.S.\n- Plain text only — no markdown formatting (asterisks and underscores render as raw characters in most email clients)\n- Subject lines: Under 50 characters, create urgency or curiosity without clickbait\n\n**Landing Page**\n\n- Structure: Headline → Subheadline → Hero section → Benefits (3-5) → Social proof placeholder → CTA → FAQ\n- Copy style: Benefit-driven, scannable, action-oriented\n- Include: Primary CTA copy and secondary CTA copy\n- SEO: Target keyword in headline and meta description\n\n**Press Release**\n\n- Structure: Headline → Dateline → Lead paragraph (who, what, when, where, why) → Body (quotes, context, details) → Boilerplate → Contact info\n- Tone: Factual, third-person, newsworthy angle\n- Length: 400-600 words\n- Include: One executive quote, one supporting quote (customer\u002Fpartner if applicable)\n\n**Case Study**\n\n- Structure: Customer overview → Challenge → Solution → Results → Quote → CTA\n- Results: Quantified where possible (%, time saved, revenue impact)\n- Length: 600-1200 words\n- Tone: Factual but narrative; let the customer be the hero\n\n### Step 3: Research and Hook\n\nBefore writing:\n\n1. Search for relevant context if connected sources are available\n2. Identify the strongest hook — what makes this worth reading?\n3. Check for competing content on the same topic — what angle is not yet covered?\n\nHook types:\n\n- Contrarian: Challenge a common assumption\n- Data-led: Open with a surprising statistic\n- Story: Start with a specific scenario the reader recognises\n- Question: Ask a question the reader wants answered\n- Urgency: Frame a time-sensitive opportunity or risk\n\n### Step 4: Draft\n\nWrite the full draft following the content type structure. Apply these principles:\n\n- Lead with value — the reader's benefit comes before your product\n- One idea per paragraph — don't stack multiple points\n- Active voice — \"We launched...\" not \"It was launched by...\"\n- Specific over general — \"37% faster\" not \"significantly faster\"\n- Show, don't tell — examples and scenarios over abstract claims\n\n### Step 5: Self-Review\n\nBefore presenting the draft, check:\n\n- Does the opening hook earn the next sentence?\n- Is the key message clear within the first 20% of the content?\n- Does every section serve the stated goal?\n- Is the CTA specific and actionable?\n- Does the tone match the brand\u002Faudience?\n- Are all claims supported by provided facts (not fabricated)?\n- Is it the right length for the content type?\n\n---\n\n## Output Format\n\nPresent the draft with clear metadata:\n\n```\n## [Content Type]: [Title \u002F Subject]\n\n**Audience:** [Target reader]\n**Goal:** [Desired action or outcome]\n**SEO keyword:** [If applicable]\n**Word count:** [Approximate]\n\n---\n\n[Full draft content here]\n\n---\n\n**Notes:**\n- [Assumptions made]\n- [Sections that need client input — quotes, data, approval]\n- [Suggested visuals or supporting assets]\n```\n\n---\n\n## Guardrails\n\n- Never fabricate statistics, quotes, or case study results. Use only data from the user; mark placeholders clearly: [INSERT: customer quote about results].\n- No markdown formatting in email drafts. Email clients render asterisks and underscores as raw characters — use plain text and line breaks.\n- Skip generic openings. \"In today's fast-paced world…\" and \"Are you looking for…\" — start with the hook.\n- Ask about the audience before drafting. A blog post for CTOs reads very differently from one for junior developers.\n\n---\n\n## After Drafting\n\nAsk:\n\n- \"Want me to create variants for a different channel?\"\n- \"Should I write the social media posts to promote this blog post?\"\n- \"Want me to optimise this draft for a specific SEO keyword?\"\n- \"Should I adapt this for a different audience segment?\"\n- \"Want me to check this against your brand voice guidelines?\"\n\n> **Tip:** Request DOCX or Markdown output via companyFILES to get a formatted, instantly shareable draft.\n","# Content Draft Skill\n\nGenerate first-draft marketing content across six content types. Each type follows channel-specific best practices for structure, length, and tone. Output is always a working first draft ready for human review and refinement — not a final publish-ready piece.\n\n## Where the Data Comes From\n\n| Source | What It Adds |\n| --- | --- |\n| **CMS via MCP** | Existing content for tone matching and internal linking |\n| **Brand guidelines via companyRAG \u002F file upload** | Voice, tone, terminology, visual style rules |\n| **Analytics via MCP** | Top-performing content patterns for the audience |\n\n> **No connected source?** Provide the data in chat or upload the relevant files — the skill works the same way.\n\n---\n\n## Workflow\n\n### Step 1: Gather Brief\n\nBefore drafting, clarify:\n\n1. Content type — blog post, social media, email, landing page, press release, or case study\n2. Topic or subject — what is this about?\n3. Target audience — who reads this? (persona, job role, stage in funnel)\n4. Goal — what should the reader do or feel after reading? (awareness, click, sign up, share)\n5. Key messages — 1-3 points that must be communicated\n6. Tone — formal, conversational, playful, authoritative? (load brand guidelines if available)\n7. Constraints — word count, required CTAs, SEO keywords, compliance disclaimers\n\nProceed with partial answers. Note assumptions.\n\n### Step 2: Route by Content Type\n\nEach content type has different structural requirements:\n\n**Blog Post**\n\n- Length: 800-2000 words depending on depth\n- Structure: Hook → Context → Main argument (with subheadings) → Takeaway → CTA\n- Include: H2\u002FH3 hierarchy, scannable paragraphs (3-4 sentences max), one CTA\n- SEO: Target keyword in title, H1, first 100 words, meta description\n- Tone: Match the publication's voice; default to informative and approachable\n\n**Social Media**\n\n- Produce variants for each platform requested:   - LinkedIn: 150-300 words, professional, hook in first line, 3-5 hashtags   - X\u002FTwitter: Under 280 characters, punchy, optional thread format for longer content   - Instagram: Caption 125-200 words, visual hook, relevant hashtags (10-15)\n- Structure: Hook line → Value → CTA\n- Include: 2-3 variants per platform with different angles\n\n**Email**\n\n- Length: 150-400 words body text\n- Structure: Subject line (3-5 variants) → Preview text → Opening hook → Body → CTA → P.S.\n- Plain text only — no markdown formatting (asterisks and underscores render as raw characters in most email clients)\n- Subject lines: Under 50 characters, create urgency or curiosity without clickbait\n\n**Landing Page**\n\n- Structure: Headline → Subheadline → Hero section → Benefits (3-5) → Social proof placeholder → CTA → FAQ\n- Copy style: Benefit-driven, scannable, action-oriented\n- Include: Primary CTA copy and secondary CTA copy\n- SEO: Target keyword in headline and meta description\n\n**Press Release**\n\n- Structure: Headline → Dateline → Lead paragraph (who, what, when, where, why) → Body (quotes, context, details) → Boilerplate → Contact info\n- Tone: Factual, third-person, newsworthy angle\n- Length: 400-600 words\n- Include: One executive quote, one supporting quote (customer\u002Fpartner if applicable)\n\n**Case Study**\n\n- Structure: Customer overview → Challenge → Solution → Results → Quote → CTA\n- Results: Quantified where possible (%, time saved, revenue impact)\n- Length: 600-1200 words\n- Tone: Factual but narrative; let the customer be the hero\n\n### Step 3: Research and Hook\n\nBefore writing:\n\n1. Search for relevant context if connected sources are available\n2. Identify the strongest hook — what makes this worth reading?\n3. Check for competing content on the same topic — what angle is not yet covered?\n\nHook types:\n\n- Contrarian: Challenge a common assumption\n- Data-led: Open with a surprising statistic\n- Story: Start with a specific scenario the reader recognises\n- Question: Ask a question the reader wants answered\n- Urgency: Frame a time-sensitive opportunity or risk\n\n### Step 4: Draft\n\nWrite the full draft following the content type structure. Apply these principles:\n\n- Lead with value — the reader's benefit comes before your product\n- One idea per paragraph — don't stack multiple points\n- Active voice — \"We launched...\" not \"It was launched by...\"\n- Specific over general — \"37% faster\" not \"significantly faster\"\n- Show, don't tell — examples and scenarios over abstract claims\n\n### Step 5: Self-Review\n\nBefore presenting the draft, check:\n\n- Does the opening hook earn the next sentence?\n- Is the key message clear within the first 20% of the content?\n- Does every section serve the stated goal?\n- Is the CTA specific and actionable?\n- Does the tone match the brand\u002Faudience?\n- Are all claims supported by provided facts (not fabricated)?\n- Is it the right length for the content type?\n\n---\n\n## Output Format\n\nPresent the draft with clear metadata:\n\n```\n## [Content Type]: [Title \u002F Subject]\n\n**Audience:** [Target reader]\n**Goal:** [Desired action or outcome]\n**SEO keyword:** [If applicable]\n**Word count:** [Approximate]\n\n---\n\n[Full draft content here]\n\n---\n\n**Notes:**\n- [Assumptions made]\n- [Sections that need client input — quotes, data, approval]\n- [Suggested visuals or supporting assets]\n```\n\n---\n\n## Guardrails\n\n- Never fabricate statistics, quotes, or case study results. Use only data from the user; mark placeholders clearly: [INSERT: customer quote about results].\n- No markdown formatting in email drafts. Email clients render asterisks and underscores as raw characters — use plain text and line breaks.\n- Skip generic openings. \"In today's fast-paced world…\" and \"Are you looking for…\" — start with the hook.\n- Ask about the audience before drafting. A blog post for CTOs reads very differently from one for junior developers.\n\n---\n\n## After Drafting\n\nAsk:\n\n- \"Want me to create variants for a different channel?\"\n- \"Should I write the social media posts to promote this blog post?\"\n- \"Want me to optimise this draft for a specific SEO keyword?\"\n- \"Should I adapt this for a different audience segment?\"\n- \"Want me to check this against your brand voice guidelines?\"\n\n> **Tip:** Request DOCX or Markdown output via companyFILES to get a formatted, instantly shareable draft.\n",{"name":5,"description":7},"main","39e0752000720de2d20917bd46c1c5149c4a0221","en\u002Fskills\u002Fmarketing\u002Fcontent-draft-skill","https:\u002F\u002Fgithub.com\u002FinnFactory-AI\u002Fcompany-ai-stack-skills","https:\u002F\u002Fgithub.com\u002FinnFactory-AI","https:\u002F\u002Finnfactory.ai","Engineering AI. Enabling Tomorrow.","2026-11-13 19:54:47",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add innFactory-AI\u002Fcompany-ai-stack-skills --skill content-draft-skill",{"tool":38,"command":39},"bunx","bunx skills add innFactory-AI\u002Fcompany-ai-stack-skills --skill content-draft-skill",{"tool":41,"command":42},"pnpm","pnpm dlx skills add innFactory-AI\u002Fcompany-ai-stack-skills --skill content-draft-skill","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FinnFactory-AI\u002Fcompany-ai-stack-skills\u002Fblob\u002Fmain\u002Fen\u002Fskills\u002Fmarketing\u002Fcontent-draft-skill\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7AF4HHK5B987T44HW7BZFVZ","sales-asset-skill","Produce tailored one-pagers, landing pages, case study drafts, and demo narratives personalised to a specific deal and buyer persona. Use when preparing collateral for a specific deal, building leave-behind materials, or customising standard assets for a prospect. Trigger with \"create a one-pager for\", \"sales deck for [deal]\", \"customise this asset for\".","https:\u002F\u002Fgithub.com\u002FinnFactory-AI\u002Fcompany-ai-stack-skills\u002Fblob\u002Fmain\u002Fen\u002Fskills\u002Fsales\u002Fsales-asset-skill\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7AF4D32V0FJE0QGCBZSQ7BW","pipeline-review-skill","Analyse deal health, surface stale or at-risk opportunities, and produce a prioritised weekly action plan. Use when preparing for a pipeline review meeting, assessing forecast accuracy, or identifying stuck deals. Trigger with \"review my pipeline\", \"pipeline health check\", \"deal risk analysis\".","https:\u002F\u002Fgithub.com\u002FinnFactory-AI\u002Fcompany-ai-stack-skills\u002Fblob\u002Fmain\u002Fen\u002Fskills\u002Fsales\u002Fpipeline-review-skill\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7AF48W7G8DMAHRAM125B192","outreach-skill","Research a prospect then draft personalised outreach with research-backed hooks, subject-line variants, and follow-up sequences. Use when cold-emailing a prospect, writing LinkedIn outreach, or building a multi-touch sequence. Trigger with \"draft outreach to [person\u002Fcompany]\", \"write cold email to\", \"outreach sequence for\".","https:\u002F\u002Fgithub.com\u002FinnFactory-AI\u002Fcompany-ai-stack-skills\u002Fblob\u002Fmain\u002Fen\u002Fskills\u002Fsales\u002Foutreach-skill\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7AF43VKNPQ7G1NTQ4MRH40J","forecast-skill","Build a weighted revenue forecast with risk flags, commit recommendations, and gap-to-quota analysis. Use when preparing for a forecast call, evaluating end-of-quarter projections, or assessing pipeline coverage. Trigger with \"build forecast\", \"forecast for this quarter\", \"where do I stand against quota\".","https:\u002F\u002Fgithub.com\u002FinnFactory-AI\u002Fcompany-ai-stack-skills\u002Fblob\u002Fmain\u002Fen\u002Fskills\u002Fsales\u002Fforecast-skill\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7AF3Z5N61VYSEJRYWXR4JP1","deal-strategy-skill","Map stakeholder power dynamics, surface deal risks, and recommend a step-by-step engagement strategy. Use when entering a complex deal, preparing for an executive sponsor meeting, or diagnosing a stuck opportunity. Trigger with \"plan deal strategy for\", \"stakeholder map\", \"how do I advance this deal\".","https:\u002F\u002Fgithub.com\u002FinnFactory-AI\u002Fcompany-ai-stack-skills\u002Fblob\u002Fmain\u002Fen\u002Fskills\u002Fsales\u002Fdeal-strategy-skill\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7AF3VGG29AX0T2X9WQ5MWDN","call-summary-skill","Extract action items, key topics, and objections from call notes or transcripts and draft a customer-facing follow-up email. Use after a sales call, demo, or discovery session. Trigger with \"summarise this call\", \"call notes from\", \"write follow-up for this meeting\".","https:\u002F\u002Fgithub.com\u002FinnFactory-AI\u002Fcompany-ai-stack-skills\u002Fblob\u002Fmain\u002Fen\u002Fskills\u002Fsales\u002Fcall-summary-skill\u002FSKILL.md",[],[]]