team-marketing
Skill0 starsChanged 4 months agoMITView on GitHub
Use when working on store pages, community management, social media strategy, press kits, trailer planning, or player acquisition. Routes to the correct workflow pattern and executes step-by-step.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- phoenixvn/claude-code-agencytheir own version, first seen Apr 11, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- phoenixvn/claude-code-agency★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository68 other files it gives its agents.
- adoptSkill
- architecture-decisionSkill
- architecture-reviewSkill
- art-bibleSkill
- asset-specSkill
- brainstormingSkill
- bug-reportSkill
- bug-triageSkill
- code-reviewSkill
- consistency-checkSkill
- content-auditSkill
- create-architectureSkill
- create-control-manifestSkill
- create-epicsSkill
- create-storiesSkill
- day-one-patchSkill
- design-reviewSkill
- design-systemSkill
- dev-storySkill
- dispatching-parallel-agentsSkill
- estimateSkill
- executing-plansSkill
- finishing-a-development-branchSkill
- gate-checkSkill
- goal-add-minorSkill
- goal-checkSkill
- goal-setSkill
- godot-engineSkill
- helpSkill
- map-systemsSkill
- narrative-designerSkill
- project-stage-detectSkill
- propagate-design-changeSkill
- qa-planSkill
- quick-designSkill
- red-flag-scanSkill
- regression-suiteSkill
- retrospectiveSkill
- review-all-gddsSkill
- safety-pushSkill
- scope-checkSkill
- security-auditSkill
- session-closeSkill
- setup-engineSkill
- sprint-planSkill
- startSkill
- story-doneSkill
- story-readinessSkill
- subagent-driven-developmentSkill
- systematic-debuggingSkill
- team-artSkill
- team-audioSkill
- team-combatSkill
- team-economySkill
- team-infraSkill
- team-levelSkill
- team-narrativeSkill
- team-polishSkill
- team-releaseSkill
- team-securitySkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 29
Read production/workstreams/marketing.md — what's done, in-progress, next
- Distinctive: line 30
Ask or infer: which ACTIVITY?
- Very specific: line 31
Follow the matching execution chain from team-orchestrator.md
≈ “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.
Files
Team Marketing
🌱 ShiningPlague-authored. No upstream version exists. Team-orchestrator skill for the marketing workstream.
Execution protocol: .claude/docs/templates/team-orchestrator.md
Workstream state: production/workstreams/marketing.md
Domain code: MK
If an artifact named here is absent: say so plainly in one line, skip that step, and continue. Never invent the file to satisfy a checklist, and never fail a close because an optional artifact was never created.
Step 0: Load State + Select Activity
- Read
production/workstreams/marketing.md— what's done, in-progress, next - Ask or infer: which ACTIVITY? (Design / Build / Content / Playtest / Review / Ship)
- Follow the matching execution chain from
team-orchestrator.md
Agent Routing — WHO to dispatch at each step
| Step in chain | Agent to dispatch | What they do |
| Design: strategy | community-manager | Social media plan, community engagement strategy |
| Design: launch timeline | producer | Launch timeline coordination, milestone alignment |
| Build: store page | community-manager | Store page copy, screenshots, descriptions |
| Build: press kit | community-manager | Press kit assembly, media assets |
| Content: comms | community-manager | Devlogs, social posts, patch notes |
| Review: pillars check | creative-director | Gate CD-PILLARS |
Gates to Fire
| Gate | When | Director |
| CD-PILLARS | Marketing must represent the game's identity accurately | creative-director |
Project-Specific Context
Fill in for your project (examples):
- Team shape + channels (e.g. solo indie — storefront page, social media, devlogs)
- Market research notes, if the project keeps any (name the location here)
- Launch strategy constraint (e.g. launch a testable slice and iterate on market signal)
- Asset production approach (e.g. designer generates promotional art with AI tools)
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
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.