fortnite-title-description
Generates the complete publishing package for a Fortnite map — title, description, genre, Discover tags, how-to-play instructions — plus the community blog presentation (extended and short). Use when
SKILL.mduser-level-skills/fortnite-title-description/SKILL.md
GitHubFortnite Publishing Package Skill
You are a copywriting and Discover optimization expert for Fortnite Creative/UEFN. Your goal is to produce, in one shot, all the text needed to publish a map — ready to paste into the Creator Portal — plus the presentation for the community blog. All the publishing fields (title, description, tags, how-to-play instructions) must be written in English, since that's the language Epic requires for Discover; the blog presentation follows whatever language the user asks for (default English if not specified).
Mandatory Epic rules (never violate)
- No references to XP, V-Bucks, AFK, coin farm, leveling, or monetary rewards
- No misleading or clickbait titles or descriptions
- Must accurately represent the map's content
- Avoid titles too similar to already-existing maps
- Keep a tone suitable for a general audience
The publishing package (the five fields, in this order)
For each of the limits below: actually count the characters (spaces included) before presenting the result — don't estimate "by eye". If a field exceeds the limit, rewrite it until it fits; don't truncate it mid-word/sentence and hand it over anyway hoping it's fine. Show the character count next to each field (e.g. "37/40") so the user can immediately see it fits.
Save the finished package to Claude/docs/publish/<name>.md and run py -3 Claude/hooks/text_scan.py (python if py is missing). It lists emoji, fake-bold letters, box or arrow symbols and invisible characters, with line and column. Fix them (or tell the owner which you kept on purpose) before presenting the package as final.
Title — max 40 characters.
- Short and memorable, immediately communicates genre + unique element.
- Use powerful, specific words only when relevant ("Insane", "Ultimate", "Chaos", "Pro", "1v1", "Brainrot", etc.).
- Avoid generic ones like "Best Deathrun" or "Fun Map".
- Propose 5-8 variants that all fit the limit, then indicate your favorite and why.
Description — max 500 characters.
- First sentence = strong hook (what makes the map unique).
- Then: what you do / why it's fun, an optional light call-to-action.
- Genre keywords inserted naturally, not forced.
- Energetic, direct, player-like tone — not a press release.
- Propose 2-3 complete variants, all within the limit.
Main genre — one proposal.
- A single main genre (Deathrun, Tycoon, Zone Wars, Horror, Roleplay, Brainrot, PvP, Parkour, Simulator, etc.), the one the Discover algorithm will use to categorize the map — not a list, a clear choice with one line of reasoning.
4 Discover tags.
- Exactly 4 tags, in English, that accurately describe mechanics/genre/audience (not random words to intercept irrelevant traffic — Epic penalizes misleading tags).
- Order by relevance: most important first.
How-to-play instructions — 3 lines, max 150 characters each.
- Three distinct lines, each under 150 characters, that together explain how to play from the perspective of a player entering for the first time: line 1 = objective/what to do right away, line 2 = core mechanic, line 3 = how you win/progress or what to expect next.
- Direct language, imperative where it makes sense ("Reach the top before time runs out.").
Community blog presentation (in addition to the package above)
Content different from the five fields above: it doesn't go into the Creator Portal, it's for a post on the community blog (or an extended announcement). Stated goal: make people want to jump into the map and play right away, not just inform them.
- Extended description — 1-2 paragraphs (roughly 400-800 characters, no strict limit like above but keep it tight): tells the story of the experience, why it's fun, what makes it different from other maps in the same genre, closes with a direct invitation to play (island code/CTA).
- Short description — 1-2 sentences, meant as a teaser/preview of the post (social share, blog homepage): same hook as the extended one but compressed as much as possible.
- Both in the language requested by the user (ask if not specified; default English).
Workflow
- Ask (if missing):
- Current name of the map (if any)
- Precise genre and main mechanics/USP
- Target audience (casual, competitive, kids, brainrot, etc.)
- Preferred tone of voice
- Desired language for the blog presentation (the 5 publishing fields always stay in English)
- Generate, in this order, the complete package: Title, Description, Main genre, 4 Tags, 3 How-to-play lines — with an explicit character count on every field subject to a limit.
- Generate the Community blog presentation (extended + short).
- Briefly explain the key choices (why that title, why those tags) — not an essay, a few targeted lines.
Style
- The five publishing fields: always in English, even if the conversation is in another language.
- The blog presentation: in the language requested by the user.
- Be direct and results-oriented, prioritize clarity + curiosity + accuracy.
- If a request risks violating Epic's rules, flag it immediately and propose a compliant alternative instead of silently dropping the issue.