agentleFS
mocchaleramocchalera/video-os-v2/.agents/skills/vertical-social-platform-delivery/SKILL.md

vertical-social-platform-delivery

Skill4 starsChanged 2 months agoMITView on GitHub

Select an evidence-backed platform delivery profile, preserve organic and ads scope boundaries, and produce safe-zone QA input with an explicit human preview gate when evidence is unknown or stale.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep organic and ads profiles separate.

    line 13
  2. Distinctive:

    Treat regression as an artifact check for known anchors, captions, content, and profile overlays.

    line 20

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Vertical Social Platform Delivery

Select the registered platform and surface profile before delivery review. Keep profile evidence, freshness, safe-zone geometry, fallback, and human preview separate from the render and from the platform's own preview.

Inspection order

  1. Select the exact platform, surface, and delivery variant under delivery_profiles/platform-safe-zone. Read source URL, retrieved date, published date, owner, evidence status, scope, supersession, and profile hash.
  2. Keep organic and ads profiles separate. Reject an ads profile for an organic surface and reject organic evidence as an ads measurement.
  3. For a verified profile, verify device evidence, viewport/output geometry, pixel density, UI and safe regions, method, confidence, screenshot path, and SHA256. Use the existing visual-status producer, which loads the registered profile and runs its regression runtime, before delivery review:

    npx tsx scripts/caption-review.ts visual-status --project <project> --safe-zone-profile <project-relative-profile>
  4. For partial, unavailable, stale, or unknown evidence, keep regions unknown, select the registered fallback, and require a human platform preview. Do not infer or add coordinates.
  5. Treat regression as an artifact check for known anchors, captions, content, and profile overlays. The human platform preview is a separate gate and is required whenever the profile says so.

Evidence acquisition

When a current measurement is authorized, record platform, surface, iOS or Android, device, viewport resolution, pixel density, notch or insets, app version and build, locale, and measurement date. Use a rights-cleared test clip, capture a lossless screenshot, record its SHA256, and record the measurement method and confidence. Check viewer variants separately, isolate ads from organic, and retain unknown status when any required evidence is absent or stale.

Checks

Run npm run validate:all-local, npm run typecheck, and npm run verify. Inspect delivery_profiles/platform-safe-zone and the safe-zone regression result (platform-safe-zone-qa/v1) when emitted by the runtime and route receipt; do not invent a separate receipt file. Keep platform preview evidence and renderer output as separate artifacts; this skill does not authorize compositor or Studio UI work.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.