Install
$ agentstack add skill-b2bforce-b2bforce-marketing-content-blog-post ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Blog Post Generation
Long-form draft pipeline for a content idea of type blog_post.
When to Use
- Idea file has
content_type: blog_post - User asks to write/expand a blog idea
Prerequisites
- Content idea:
workspace/marketing/content/ideas/blog_post--{buying_stage}--{slug}.md - Firm, service, ICP, persona context in workspace
- Current agent/LLM session
- Optional: Exa reference notes via
tool-exafor market-informed long-form drafts
Prompt layering (order matters)
- Base writer — style, storytelling, anti-AI-slop (no length)
- Quality layer — universal quality + buying-mode tone
- Blog format layer — authoritative length/structure →
references/format-requirements.md
Optional: workspace/firm/content-guidelines/blog-post.md if exists (company overrides).
Follow the shared draft gate and writing quality rules in docs/content-generation.md.
Research
Optional Exa reference articles: search 5 results on idea title via tool-exa; include highlights for benchmarking. Do not plagiarize.
Skip this step when the user wants a quick internal-context draft.
User prompt template
Write a Blog Post based on this content idea. Follow FORMAT REQUIREMENTS exactly.
=== CONTENT IDEA ===
Title: {title}
Description: {description}
Buying Stage: {stage label}
Buyer question: {buyer_question}
Unique angle: {unique_angle}
Proof source: {proof_source}
Next action: {next_action}
Research mode: {research_mode}
Target keyword: {if any}
=== CONTEXT ===
{company, service, ICP, persona from workspace}
=== REFERENCE ARTICLES ===
{exa results or none}
Requirements:
- 800-1500 words, Markdown H2/H3
- Match buying stage framework (see format requirements)
- Brand voice from firm profile
- Hook opening — no generic intro
- Use proof only from workspace, idea proof_source, or reference notes
- CTA aligned to buying stage
- Language: {language}
Return JSON: { "title": "...", "body": "markdown..." }
Output
workspace/marketing/content/drafts/blog/{slug}.md
Frontmatter: idea, content_type, buying_stage, service, icp, persona, target_keyword, generated_at.
Run scripts/validate-content-draft.sh {output}. Update idea frontmatter to status: generated after the draft validates.
Related Skills
marketing-content-ideas (upstream) | other marketing-content-* for different types
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: b2bforce
- Source: b2bforce/b2bforce
- License: MIT
- Homepage: https://www.b2bforce.ai/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.