Trader Memory Core
tradermonty/claude-trading-skills
Track investment theses across their lifecycle — from screening idea to closed position with postmortem.
Plan an independent music release backwards from release day — the 8-week countdown with distributor upload deadlines flagged, playlist pitch windows, the pre-save decision made honestly, content…
Install Release Day Countdown
$ npx skills add mohitagw15856/pm-claude-skills --skill release-day-countdown -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills release-day-countdown --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/release-day-countdown .claude/skills/release-day-countdown && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "release-day-countdown" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/release-day-countdown into .claude/skills/release-day-countdown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-day-countdown", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/release-day-countdownType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill release-day-countdown -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills release-day-countdown --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/release-day-countdown .agents/skills/release-day-countdown && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "release-day-countdown" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/release-day-countdown into .agents/skills/release-day-countdown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-day-countdown", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill release-day-countdown -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills release-day-countdown --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/release-day-countdown .cursor/skills/release-day-countdown && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "release-day-countdown" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/release-day-countdown into .cursor/skills/release-day-countdown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-day-countdown", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/release-day-countdown--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill release-day-countdown -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills release-day-countdown --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/release-day-countdown .gemini/skills/release-day-countdown && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "release-day-countdown" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/release-day-countdown into .gemini/skills/release-day-countdown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-day-countdown", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills release-day-countdownInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill release-day-countdown -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/release-day-countdown .github/skills/release-day-countdown && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "release-day-countdown" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/release-day-countdown into .github/skills/release-day-countdown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-day-countdown", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill release-day-countdown -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills release-day-countdown --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/release-day-countdown .opencode/skills/release-day-countdown && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "release-day-countdown" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/release-day-countdown into .opencode/skills/release-day-countdown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-day-countdown", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
release-day-countdown- GitHub stars
- 1.4k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 776 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Plan an independent music release backwards from release day — the 8-week countdown with distributor upload deadlines flagged, playlist pitch windows, the pre-save decision made honestly, content…
- Works in 5 steps: Pick the date like a logistics decision.… → Weeks 8–6: finish and upload. Master… → Weeks 5–3: batch the content while calm.… → …
- A musician says Im releasing a single/EP
- SKILL.md covers What This Skill Produces, Required Inputs, Framework and Output Format, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Release Day Countdown is an agent skill from mohitagw15856/pm-claude-skills. Plan an independent music release backwards from release day — the 8-week countdown with distributor upload deadlines flagged, playlist pitch windows, the pre-save decision made honestly, content batched before the chaos, and a release week that doesn't depend on luck. Use when a musician says 'I'm releasing a single/EP', 'when should I submit to playlists', 'plan my release', or uploaded to a distributor with no plan. Produces the week-by-week countdown, the asset checklist, and release-week runbook.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud, covering Runbooks and postmortems. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- A musician says Im releasing a single/EP
- Should I submit to playlists
- Plan my release
- Uploaded to a distributor with no plan
Example prompts
- “t depend on luck. Use when a musician says”
- “m releasing a single/EP”
- “when should I submit to playlists”
- “/release-day-countdown”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Pick the date like a logistics decision. Fridays are conventional
- Weeks 8–6: finish and upload. Master finalized · artwork at spec ·
- Weeks 5–3: batch the content while calm. The pitch text (one
- Weeks 2–1: outreach in person-sized batches. Independent curators
- Release week: the runbook, not vibes. Day 0: everything live,
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Release Day Countdown loads about 1.6k tokens when it runs. Until then it costs about 132 tokens; SKILL.md has 776 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 776 words, ~1,644 tokens.
Download SKILL.mdSave it as
.claude/skills/release-day-countdown/SKILL.md (or your agent's skills folder).- name
- release-day-countdown
- description
- Plan an independent music release backwards from release day — the 8-week countdown with distributor upload deadlines flagged, playlist pitch windows, the pre-save decision made honestly, content batched before the chaos, and a release week that doesn't depend on luck. Use when a musician says 'I'm releasing a single/EP', 'when should I submit to playlists', 'plan my release', or uploaded to a distributor with no plan. Produces the week-by-week countdown, the asset checklist, and release-week runbook.
Release Day Countdown Skill
Most independent releases happen twice: the day the song goes live to 40 streams, and the month later when the artist learns what they should have done eight weeks early. The machinery has real deadlines — distributors need lead time, editorial playlist pitching closes before release day, content is impossible to batch once the week arrives — and none of it is complicated; it's just sequenced. This skill runs the sequence backwards from the date (or forwards to pick a date honestly), with every platform-specific number flagged as check-current, because lead times and pitch windows change and a plan built on stale specifics is a plan built on sand.
What This Skill Produces
- The 8-week countdown, week by week: distribution upload, metadata and credits, pitch windows, content batching, outreach waves — each with its why and its check-current flag where platforms set the rule
- An asset checklist: audio master, artwork at spec, canvas/visualizer, lyric assets, press photo, the bio paragraph — with the "before upload" vs "before release" split
- The pitching plan: editorial (via the distributor/platform tools, submitted early), independent curators (researched, personalized, no-pay-for-play flagged as the scam it usually is), and the local/press angle from [[press-kit-epk]]
- A release-week runbook: day-by-day, including the two moves that outperform everything (thanking early sharers personally, and the day-3 content drop when the algorithm decides)
- The honest-expectations line: what a first release's numbers typically look like, so week two isn't despair
Required Inputs
Ask for (if not already provided):
- The release: single/EP/album, genre, done-ness of the master and artwork, the date (or "help me pick one")
- The artist's current reach, honestly: platforms, follower counts, the mailing list if any, past release numbers
- Team of one, or help? Budget: zero, small, or real?
- The goal, honestly ranked: streams? local gigs? label attention? the mailing list? (The plan weights differently)
Framework
- Pick the date like a logistics decision. Fridays are conventional (chart weeks) but a small artist's Tuesday can dodge the big-release flood — decide by goal. Then anchor the two hard deadlines backwards: distributor upload (lead times vary — check yours, typically weeks not days) and editorial pitch close (before release; check the platform's current window). Everything else hangs between.
- Weeks 8–6: finish and upload. Master finalized · artwork at spec · metadata and credits complete (wrong credits are forever) · upload early — early upload is what makes editorial pitching possible at all.
- Weeks 5–3: batch the content while calm. The pitch text (one paragraph: what it is, what it's like, one true story) · 10–15 content pieces from the one song (teasers, the story behind it, the lyric moment, the bad-first-demo comparison people love) · the pre-save decision made honestly: pre-saves help algorithmic day-one but annoy small audiences if over-flogged — one ask, two reminders, done.
- Weeks 2–1: outreach in person-sized batches. Independent curators researched (right genre, real playlists with real listeners), personalized two-line pitches · local press/radio with the EPK · the mailing list gets the real story, not the marketing copy — the list is the only channel the artist owns, treat it best.
- Release week: the runbook, not vibes. Day 0: everything live, links verified, the personal-thanks discipline starts (every share answered by name — it's the highest-ROI hour in music marketing). Day 3: the held-back content drop. Day 7: numbers reviewed against honest expectations, thank-you post, and the next release sketched — because catalogs compound and one-offs don't.
Show full SKILL.md (216 more words)Show less
Output Format
## The countdown — [release] on [date]
| Week | Must ship | Platform deadlines (check-current) | Content batch |
## Asset checklist
[Before-upload set · before-release set · specs flagged check-current]
## Pitching plan
[Editorial route · curator shortlist criteria + the 2-line pitch ·
press/local via EPK · the no-pay-for-play warning]
## Release week runbook
[Day by day · the personal-thanks discipline · the day-3 drop]
## Honest expectations + next
[What week one typically looks like at your reach · the catalog note]Quality Checks
- Every platform-specific number (lead times, pitch windows, artwork specs) carries a check-current flag — zero asserted as timeless fact
- The countdown fits the real date; if the date makes editorial pitching impossible, the plan says so and offers the honest choice (move the date or skip that channel)
- Content is batched before week 2 in the plan — nothing creative is scheduled for release week itself
- The pay-for-playlist warning appears in the pitching plan
- Expectations are calibrated to the artist's actual current reach
Anti-Patterns
- Do not build the plan around going viral — the plan works at 40 streams and scales if lightning hits, not the reverse
- Do not recommend paid playlist placement or stream-farming — flagged as harmful (platforms penalize it), not just tacky
- Do not schedule daily begging posts — the ask-budget is finite; story content spends it better than reminders
- Do not skip credits/metadata rigor — it's the least fun item and the most permanent
- Do not let release day end the plan; the day-7 review and next- release sketch are in the runbook
Related
[[press-kit-epk]] for the outreach attachment; [[band-agreement]] before the money arrives; [[clip-factory]] turns the one song into the fifteen pieces; [[content-calendar]] for the ongoing rhythm after.
Example Trigger Phrases
- "I'm releasing a single/EP."
- "Should I submit to playlists?"
- "Plan my release."
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/release-day-countdown of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Release Day Countdown next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Release Day Countdown this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Trader Memory Coretradermonty/claude-trading-skills | 3k | 2 repos | ~4.3k | Automated safety check: Pass | MIT | |
| Author Migrationnrwl/nx | 29k | — | ~12k | Automated safety check: Notes | MIT | |
| Write Notes Like Deepseekczm15053/write-notes-like-deepseek | 497 | — | ~2k | Automated safety check: Pass | None | |
| OpenRig Upgrade Proceduremvschwarz/openrig | 6.2k | — | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| GreptimeDB Release RunbookGreptimeTeam/greptimedb | 6.7k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Author Migration
nrwl/nx
Author or scope a first-party Nx migration. An agent skill from nrwl/nx.
Write Notes Like Deepseek
czm15053/write-notes-like-deepseek
A skill your agent uses when a change is non-trivial by DSH standards (behavior, architecture, cross-file contracts, process/tooling, testing strategy, or on-disk/wire/config formats), when choosing…
OpenRig Upgrade Procedure
mvschwarz/openrig
Walks an agent through upgrading the OpenRig CLI and daemon one observed step at a time, keeping live seats alive and reconciling managed plugin files.
GreptimeDB Release Runbook
GreptimeTeam/greptimedb
Runbook for publishing a GreptimeDB version: pick the release branch, verify the Cargo version, then tag, create the GitHub release and open the docs note PR.
Statem
henryqin1997/statem
A skill your agent uses when a long coding or research task should be managed with statem state-machine runbooks, including creating specs, starting or resuming runs, checking current state…
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Related
Categories
Questions about Release Day Countdown
What does Release Day Countdown do?
Plan an independent music release backwards from release day — the 8-week countdown with distributor upload deadlines flagged, playlist pitch windows, the pre-save decision made honestly, content…. Release Day Countdown is an agent skill from mohitagw15856/pm-claude-skills. Plan an independent music release backwards from release day — the 8-week countdown with distributor upload deadlines flagged, playlist pitch windows, the pre-save decision made honestly, content batched before the chaos, and a release week that doesn't depend on luck.
When should I use Release Day Countdown?
Release Day Countdown fits situations like: A musician says Im releasing a single/EP; should I submit to playlists; plan my release; uploaded to a distributor with no plan.
How do I install Release Day Countdown in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill release-day-countdown -a claude-code`. Or copy the skill folder (skills/release-day-countdown in mohitagw15856/pm-claude-skills) into .claude/skills/release-day-countdown in your project. Claude Code loads it when a task matches its description.
How do I install Release Day Countdown in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill release-day-countdown -a codex`. Or copy the skill folder (skills/release-day-countdown in mohitagw15856/pm-claude-skills) into .agents/skills/release-day-countdown in your project. Codex loads it when a task matches its description.
Can I use Release Day Countdown in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill release-day-countdown -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/release-day-countdown, .gemini/skills/release-day-countdown, .github/skills/release-day-countdown and .opencode/skills/release-day-countdown in your project.
What does Release Day Countdown need to run?
SKILL.md names no scripts, command-line tools or credentials: Release Day Countdown is instructions for the agent only.
Does Release Day Countdown access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Release Day Countdown safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Release Day Countdown use?
Release Day Countdown is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Release Day Countdown use?
About 1.6k tokens (SKILL.md is roughly 6.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Release Day Countdown?
Skills that share tags, products or a category with Release Day Countdown: Trader Memory Core (tradermonty/claude-trading-skills, 3k stars), Author Migration (nrwl/nx, 29k stars), Write Notes Like Deepseek (czm15053/write-notes-like-deepseek, 497 stars) and OpenRig Upgrade Procedure (mvschwarz/openrig, 6.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Release Day Countdown?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,433 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 8, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.