Install
$ agentstack add skill-b2bforce-b2bforce-marketing-content-linkedin-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
LinkedIn Post Generation
Draft pipeline for a content idea of type linkedin_post.
When to Use
- Idea with
content_type: linkedin_post - User wants LinkedIn-native copy (not cross-posted blog summary)
Prerequisites
- Content idea file + firm/service/ICP/persona context
- Current agent/LLM session
- Do NOT run Exa reference search (skipped for this type)
Prompt layering
- Base writer (style only)
- Quality layer
- LinkedIn format layer →
references/format-requirements.md
Optional: workspace/firm/content-guidelines/linkedin-post.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.
Output format (critical)
- Plain text — NOT Markdown headers
- One sentence per line
- 150–250 words optimal; max ~300 words / 3000 chars
- 0–2 emojis if brand-appropriate
- 2–3 hashtags at end
- Engagement question at end
- No bullet lists (hurts engagement)
- First-person voice (I, we, you)
Stage → framework (from format prompt)
| Stage | Framework | |-------|-----------| | Problem | Story Hook, Poll | | Concept | Category, This-vs-That | | Education | Framework, How-To | | Decision | Comparison, Data | | Vendor | CSR, Behind-the-Scenes |
Output path
workspace/marketing/content/drafts/linkedin/{slug}.md
Frontmatter: idea, content_type, buying_stage, service, icp, persona, generated_at. Body = plain text only. Title in frontmatter for filing.
Run scripts/validate-content-draft.sh {output}. Update idea frontmatter to status: generated after the draft validates.
Related Skills
marketing-content-x-post — different length/platform rules
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.