JasonColapietro/suede-creator-skills / skills/suede-social
suede-social
VerifiedPlan, audit, and draft organic social for founder/brand accounts: platform mix, 30-post audits, calendars, Instagram, LinkedIn/X, short-video scripts, social search, and listening. Use when asked to "audit our Instagram growth" or build an approval-ready content loop. NOT FOR: paid ads (use suede-ads or suede-ad-creative), editorial agents (use suede-newsroom), clip-to-guide work (use suede-clip-to-guide), video rendering (use suede-video), or broad content strategy (use suede-content-strategy).
| File | Kind | Size |
|---|---|---|
| CARD.md | markdown | 4.6 KB |
| SKILL.md | skill md | 14.2 KB |
| agents/openai.yaml | config | 643 B |
| evals/evals.json | config | 12.2 KB |
| references/account-audit.md | markdown | 5.2 KB |
| references/carousel-frameworks.md | markdown | 10.4 KB |
| references/content-production.md | markdown | 3.3 KB |
| references/daily-loop.md | markdown | 2.9 KB |
| references/listening-sources-template.md | markdown | 3.9 KB |
| references/listening.md | markdown | 12.8 KB |
| references/measurement.md | markdown | 2.8 KB |
| references/platform-limits.md | markdown | 3.0 KB |
| references/platforms.md | markdown | 7.0 KB |
| references/post-templates.md | markdown | 3.8 KB |
| references/reverse-engineering.md | markdown | 6.4 KB |
| references/short-form-video.md | markdown | 8.6 KB |
| references/social-search.md | markdown | 3.4 KB |
| references/worked-handoff.md | markdown | 1.7 KB |
references/daily-loop.md
View on GitHub# Daily Content Loop
The daily loop produces decisions and approval-ready assets. It does not imply
automatic publishing or autonomous engagement.
## Inputs
- refreshed Account Evidence Pack;
- current content ledger and queue;
- prior post readback and due measurement checkpoints;
- active offer and conversion destination;
- audience comments, questions, DMs, search terms, and support themes the user
is authorized to access;
- current official platform guidance and account status;
- lawful trend sources and cleared media library.
## Run
1. **Read yesterday.** Record post status, early measures, comments needing
human review, and any broken link or render issue. Do not draw a performance
conclusion before the named checkpoint.
2. **Refresh signals.** Capture only relevant audience questions, account
insights, product events, owned proof, and current trends. Date every signal.
3. **Protect the queue.** Remove stale claims, expired links, duplicated angles,
rights-unclear media, and posts whose context materially changed.
4. **Select candidates.** Score ideas on audience recognition, payoff, evidence,
voice fit, and business bridge. Select 1–3 candidates with different jobs.
5. **Produce packages.** Use the short-video, carousel, Story, text, or static
contract in [content-production.md](content-production.md) and
[post-templates.md](post-templates.md).
6. **QA.** Verify exact claims, source rights, identity, accessibility, CTA,
destination, disclosure, and brand voice.
7. **Request exact approval.** Show the final copy, media list, visible identity,
destination, timing hypothesis, and any collaborator or tag.
8. **Publish only if authorized.** Use the authenticated native surface or an
approved API/tool permitted for the account.
9. **Read back.** Confirm permalink, identity, rendered media, caption, tags,
collaborator state, CTA destination, and public availability.
10. **Log.** Record post ID, publish time, experiment variable, primary metric,
measurement checkpoint, and permalink.
## Approval packet
```text
Account / visible identity:
Format:
Final media and rights source:
Final caption:
Tags / collaborators / location:
CTA and destination:
Publish time hypothesis:
Experiment variable:
Primary metric and checkpoint:
Approval status: draft | exact-content approved | published and read back
```
## Failure handling
- **No authenticated access:** return drafts and the audit worksheet.
- **Metrics missing:** label performance class `unknown` and request Insights or
attribution evidence.
- **Composer differs from plan:** stop before publish and show the rendered
difference.
- **Publish succeeds but readback fails:** report `publish state unknown`; do
not retry blindly.
- **Rights or disclosure unclear:** use the halt contract and omit the asset.
- **Comments or DMs contain threats, medical/legal/financial claims, private
data, or account-security issues:** escalate for human review; do not reply.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |