bigeasyfreeman/ship-content
skills/ship-content/SKILL.md
Orchestration skill for Magnus content delivery. Brief → Council → Draft → Slop Gate → Council(light) → Publish. End-to-end content creation and publishing.
testing
Updated Apr 27, 2026
$ install --global
skillsauthnpx skillsauth add bigeasyfreeman/adlc ship-contentInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 27, 2026, 2:55 AM55.1s1 file scanned
SKILL.md
- name:
- ship-content
- description:
- Orchestration skill for Magnus content delivery. Brief → Council → Draft → Slop Gate → Council(light) → Publish. End-to-end content creation and publishing.
Ship Content (Orchestration — Magnus)
Overview
Chains the ADLC Build Loop adapted for content operations. From content signal to published piece.
When to Use
- Magnus needs to produce and publish content
- Content brief is ready for execution
- End-to-end content creation pipeline
The Sequence
Step 1: Content Brief (structured from signal)
Step 2: Eval Council (HEAVY — content-adapted)
Step 3: Draft (content-forge with voice profile)
Step 4: Stop Slop (content mode, 35/50 gate) ←── revision loop
Step 5: Platform Adapt (each version slop-gated)
Step 6: Eval Council (LIGHT — 2 personas, 1 round)
Step 7: Publish (Postiz CLI)
Step 8: Audit + Engagement Tracking
Step 1: Content Brief
- External Magnus dependency:
content-brief(Magnus domain PRD) - Structure signal into: topic, angle, ICP target, platform, voice constraints, format, anti-slop rules
- Reject ambiguous briefs (no clear ICP, no clear angle)
Step 2: Eval Council — Full
- Skill:
eval-council(HEAVY — 6 content-adapted personas) - Architect: Content strategy alignment
- Skeptic: Brand damage risk
- Operator: Platform publishability
- Executioner: Can the agent produce this?
- Security Auditor: PII/reputation risk
- First Principles: Does this serve the ICP?
Step 3: Draft
- External Magnus dependency:
content-forge - Voice profile loaded (
eric-voice-profile.md) - Draft against brief constraints
- STRIDE brand risk awareness during drafting
Step 4: Stop Slop Gate
- Skill:
stop-slop(content mode) - 5-dimension scoring: Directness, Rhythm, Trust, Authenticity, Density
- Threshold: 35/50 (38/50 for outreach)
- If fail: revise with specific feedback on which dimensions failed
- Max 3 revision attempts, then escalate
Step 5: Platform Adapt
- External Magnus dependency:
content-adapt - Generate platform-native versions (LinkedIn, X, email, etc.)
- EACH version individually slop-gated (35/50)
- Platform constraints enforced (character limits, format rules)
Step 6: Eval Council — Light
- Skill:
eval-council(LIGHT — 2 personas, 1 round) - Skeptic: Any brand risk in final versions?
- Operator: Ready to publish across all target platforms?
Step 7: Publish
- External Magnus dependency:
content-publish - Publish via Postiz CLI
- Capture: platform, URL, timestamp, content_id
Step 8: Audit + Tracking
- Pipeline audit log: full trace from brief to publish
- Engagement tracking initiated (link to pipeline_run_id)
- Feedback capture: when Eric edits, diff is recorded for voice profile refinement
Related Skills
bigeasyfreeman/build-feature
development
VerifiedTrustedCommunity
Orchestration skill: chains the full ADLC Build Loop. PRD → Brief → Council → Scaffold → Codegen → LDD → TDD → Council → PR. Use when implementing a new feature end-to-end.
1SKILL.mdUpdated Apr 22, 2026
bigeasyfreeman/skills/helm-argocd-deployment
development
VerifiedTrustedCommunity
# Skill: Helm & ArgoCD Deployment > Validates Helm charts and generates ArgoCD Application manifests when the ADLC pipeline produces infrastructure or service code. Ensures every deployable artifact has correct chart structure, environment-specific values, and a GitOps-ready Application manifest before code review. --- ## Why This Exists Without deployment validation in the pipeline, common failures slip through to production: - **Helm charts fail `helm template`** because of missing values,
SKILL.mdUpdated May 5, 2026
bigeasyfreeman/verifier-semantic-judge
testing
VerifiedTrustedCommunity
Decide whether an intersecting verifier actually exercises the semantic change.
SKILL.mdUpdated Apr 23, 2026
bigeasyfreeman/skills/ux-flow-builder
development
VerifiedTrustedCommunity
# Skill: UX Flow Builder > Generates user flow diagrams (Mermaid) from PRD personas and screen specifications. Surfaces dead ends, missing screens, and disconnected flows before design or engineering starts. Helps PMs think in screens, not features. --- ## Trigger - Automatically during PRD Phase 4 (Personas & Flows) to visualize the user journey - On-demand when the PM says "show me the flow" or "map the user journey" - During PRD evaluation to verify screen connectivity --- ## Input ```
SKILL.mdUpdated Apr 23, 2026