skill-b2bforce-b2bforce-marketing-content-x-post · by Install
$ agentstack add skill-b2bforce-b2bforce-marketing-content-x-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.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-b2bforce-b2bforce-marketing-content-x-post) 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
X (Twitter) Post Generation
Draft pipeline for a content idea of type x_post.
When to Use
- Idea with
content_type: x_post - Single tweet or educational thread (8–12 tweets)
Prerequisites
- Content idea + context files
- Current agent/LLM session
- No Exa reference articles
Prompt layering
- Base writer
- Quality layer
- X format layer →
references/format-requirements.md
Follow the shared draft gate and writing quality rules in docs/content-generation.md. Use buyer_question, unique_angle, proof_source, next_action, and research_mode from the idea; do not write from title + description only.
Platform rules (2026 algorithm)
- No external links in tweet body (kills reach — put link in first reply if needed)
- 1–2 hashtags max, at end
- 150–250 characters optimal per tweet
- Max 280 characters per single tweet
- Threads: separate tweets with
---divider in output file - Reply/engagement hooks critical
- One idea per tweet — punchy lines
Stage → hook pattern
| Stage | Hook type | |-------|-----------| | Problem | Data hook, Question hook | | Concept | Contrarian hook | | Education | Specificity hook, List thread (8–12 tweets) | | Decision | Story hook | | Vendor | Proof hook (soft CTA, no link in body) |
Output
workspace/marketing/content/drafts/x/{slug}.md — plain text body
For threads, document tweet count in frontmatter.
Frontmatter: idea, content_type, buying_stage, service, icp, persona, generated_at. Run scripts/validate-content-draft.sh {output} and update the idea to status: generated after the draft validates.
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.