agentleFS
mtarcuremtarcure/claude-vibe-squad/.agents/skills/platform-compliance/SKILL.md

platform-compliance

Skill220 starsChanged 19 days agoMITView on GitHub

Use when a finished or near-finished media asset must be exported for a named publishing platform—retrieve current official resolution, aspect, duration, codec, loudness, caption, safe-area, overlay, and disclosure requirements, then verify the actual render against a per-platform checklist. It checks delivery-channel fit; caption authoring and jurisdictional legal review are separate.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check content-policy and disclosure rules (ads/sponsorship/AI-disclosure/age) that apply to the piece.

    line 14

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Platform Compliance

Fit a media deliverable to a platform's technical and policy requirements before publish — specs, safe areas, and rules.

Steps

  1. Pull the target platform's current spec: resolution, aspect ratio(s), duration limits, codec/bitrate, captions, loudness.
  2. Lay out for the platform's safe areas and UI overlays so nothing critical is cropped or covered.
  3. Check content-policy and disclosure rules (ads/sponsorship/AI-disclosure/age) that apply to the piece; flag anything uncertain for review.
  4. Meet accessibility requirements (captions/audio description) the platform mandates.
  5. Produce a per-platform export checklist; verify the actual file against it before publishing.

Acceptance

  • The deliverable meets the platform's current technical spec (verified, not remembered).
  • Safe areas and mandated accessibility (captions/AD) are satisfied.
  • Policy/disclosure requirements are checked; uncertainties are flagged, not assumed compliant.

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.