Index of every page on this site: llms.txt
All skills
Run it yourself

Verify a social post after publishing it: duplicate guard, live re-read against the source caption, media and link checks, public-visibility check, and a lag re-read before any second delivery. Use after every publish or schedule, and whenever a publish result is uncertain, before retrying — a failed or stuck publish can still land later, and retrying blind creates duplicates.

  • 7 files
  • 898.2 KB
  • Updated 5 days ago
  • GitHub
Use this Skill: https://skilld.dev/gh/jokerhtml/needcraft-skills/post-publish-qa

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

README.md

≈627 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Post-Publish QA

Verify a social post after publishing it — and prove it, instead of trusting the publish call's success message.

What it is

A verification method in three parts: check before you publish (right account, no duplicate, latest caption, good media), verify after you publish (live post re-read byte for byte against the source caption, media, links, and a non-owner visibility check), and handle failures without creating duplicates. It works with any publishing tool, because every check is done against the live surface.

Who it is for

Anyone who publishes or schedules social posts and wants proof the post is live, correct, and not duplicated.

Install

Copy this folder into your skills directory as post-publish-qa/. No dependencies.

How to use

  1. Keep one caption file per post as the single source of truth.
  2. Before publishing, fill in examples/pre-publish-record.md (account checked, duplicate check).
  3. After publishing, open the live post and fill in examples/verification-record.md — text match, media, links, formatting, visibility (logged-out view), duplicate check.
  4. If a publish result is uncertain, check the live surface first and never retry blind: a failed or stuck publish can still land later.
  5. Stop after three genuine verification attempts (defined in SKILL.md: ≥60 s wait, fresh reload, ≥5 min apart) and report the blocker.

Example

SKILL.md contains a complete worked example: a tutorial carousel, from pre-publish record through publish, live verification, and the PASS record — plus what would have failed it.

License

MIT. See SKILL.md frontmatter.

Disclaimer

This skill verifies what is visible on the live surface. It cannot verify platform-internal states (such as reduced distribution), which show up only in the platform's own insights or support channels.

Example images — real proof

Frame 28 of NeedCraft reel-01 as the QC pass caught it (broken: overlapping text, cut-off lines, misplaced price box) and after the fix (clean layout). Same frame, before and after — this is the check this skill exists to run.

Frame 28 — before the fix

Frame 28 — after the fix

Note: the price visible in both frames is the example product's price when the reel was made. The frames are shown as the QC record — the price itself is not the point; the layout errors are.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 90f40b1. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 4 days ago.

Activeupdated 5 days ago
Other metadata
metadata
{
  "version": "1.0.0",
  "date": "2026-11-16",
  "author": "Muhammad Saad Ranjha / NeedCraft"
}

README badge

README badge for jokerhtml/needcraft-skills/post-publish-qa