Install
$ agentstack add skill-b2bforce-b2bforce-marketing-content-case-study ✓ 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
Case Study Generation
Draft pipeline for a content idea of type case_study.
When to Use
- Idea with
content_type: case_study - Buying stage must be decision or vendor only
Prerequisites
- Valid content idea (stage check)
- Firm/service/ICP/persona context
- Current agent/LLM session
- Optional: Exa reference notes via
tool-exafor quality benchmarks - Real client proof before drafting if the idea uses placeholder proof
Prompt layering
- Base writer
- Quality layer
- Case study format layer →
references/format-requirements.md
Follow the shared draft gate and writing quality rules in docs/content-generation.md.
Proof gate
If proof_source says needs real client proof before draft, or the title contains [Client], stop. Ask for real client facts before writing:
- client name or approved anonymized label
- starting situation and business problem
- service delivered and timeline
- 2–3 real metrics, before/after facts, or qualitative outcomes
- approved quote or explicit note that no quote is available
Do not invent metrics, quote, client name, industry, timeline, or result.
PASTOR structure (required)
- P Problem — client challenge with context
- A Amplify — consequences (revenue, team, risk)
- S Solution — your process/approach
- T Transformation — results with metrics (%, $, time)
- O Offer — how reader gets similar results
- R Response — clear CTA
Must include
- 2–3 quantifiable metrics when real metrics are available; otherwise use verified
qualitative outcomes and state proof limits plainly
- At least 1 client quote only when supplied or approved
- Before vs after comparison
- Timeline of engagement
Research
Optional Exa: 5 reference case studies/articles on topic for quality benchmark (do not copy).
Output
workspace/marketing/content/drafts/case-studies/{slug}.md — Markdown
Headline pattern: "[Client Result] in [Timeframe]" or "How [Client] Achieved [Result]"
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.