agentleFS
landim32landim32/awesome-ai-skills/skills/band-streaming-launch/SKILL.md

band-streaming-launch

Skill1 starsChanged 7 months agoMITView on GitHub

Domain convention for band album campaigns — undated streaming-launch announcement posts (Spotify/Deezer/Apple Music) under posts/pendente-streaming/, with Status aguardando, promoted to a dated slot when the streaming goes live. Use for streaming-launch announcements in a band album campaign. Part of the band-album-campaign pack.

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:

    When the user reports the streaming actually went live, promote the file to a dated slot: move pendente-streaming/<rede>.md to …

    line 40

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

Band Streaming Launch — dateless posts

Convention for the subset of band album posts that cannot be tied to a fixed publication date — most notably the streaming-launch announcement ("já estamos no Spotify/Deezer/Apple Music"). Streaming platforms (Spotify, Deezer, Apple Music) require a 2–7 day review window and may release at any moment within it, so the calendar must not commit to a single launch date. Part of the band-album-campaign pack; uses the generic social-media-scheduling status aguardando.

On-disk tokens and section labels are kept verbatim (PT-BR audience); the documentation is in English.

Convention

  • The dateless post lives at <NN-track-slug>/posts/pendente-streaming/<rede>.md (one file per network; Threads still mirrors instagram.md).
  • Data: = pendente — aguardando publicação no streaming (no concrete date).
  • Status: aguardando (a status distinct from planejado/publicado/cancelado: "ready but waiting for a trigger external to the calendar").
  • Each track's pendente-streaming/ stays in that track's folder (it is about that track's streaming milestone, analogous to its launch).

Where they appear in the derived views

  • In cronograma.md (per-track and master), dateless posts go in a dedicated "Pendente — sem data" section, never inside the dated table or the Gantt.
  • In agenda.md (per-track), dateless posts appear in a dedicated "Pendente — sem data" sub-section at the top of each network section (before the dated active table), so the user spots them when scheduling.

Promotion to a dated slot

When the user reports the streaming actually went live, promote the file to a dated slot: move pendente-streaming/<rede>.md to <actual-date>/<rede>.md, update Data: and Status: publicado, and reconcile cronogramas/agenda (via social-media-scheduling).

Reusing the convention

The same convention can be reused for other genuinely dateless post types if they emerge (e.g. "post for when we hit X views") — keep them under pendente-<motivo>/.

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.