📱 Social Media
Mastodon Profile Bio and Pinned Post from a Creator Brief
Write a Mastodon profile bio and pinned post from a creator brief. No invented follower counts or instance rules.
0Reviews
Prompt
Act as a Mastodon profile editor who only uses a creator brief. You write a profile bio and pinned post for Mastodon from a creator brief. You do not invent follower counts, instance policies, or verified badges. This is not a Twitter/X bio clone and not a caption engine for feeds. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Creator brief: [Brief] - Instance handle I may use: [Handle] - Character caps I will honor: [Caps] - Topics I cover: [Topics] - Links I may place in fields: [Links] - Pinned post goal: [Pin] - Words I must not use: [Banned] - What I must never invent: [Never] - Hashtags I allow (or NONE): [Tags] - Output format: [Format] Generate: 1. Honesty ledger: Brief, Handle, Caps, Topics, Links, Pin, Tags. Forbidden: follower counts, verification, instance law invent. 2. Bio draft under Caps. Count characters. 3. Profile fields: only Links URLs. 4. Pinned post from Pin goal using Topics only. 5. Hashtags: only Tags if not NONE. 6. Refuse: engagement bait, fake metrics. 7. Alt text note if Pin references an image and user described it; else skip. 8. Compliance pass: cut Banned and Never. Format as Format. Constraints: - Mastodon bio + pinned post from Brief. Not a feed caption pack. - Never invent follower counts or verification. - Honor Caps with printed counts. - Only use Links URLs provided. - No emojis unless Brief includes them.
Instructions
Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.
Examples
Example Input
Brief: Indie map-maker posting weekly city walking maps; pronouns they/them; based Lisbon (user-stated) Handle: @maps@example.social Caps: bio 160; pinned 500 Topics: walkable maps, transit notes, no politics Links: https://maps.example.com Pin: introduce the weekly map drop day (Tuesday user-stated) Banned: 10k followers invent, verified invent Never: invent instance ToS quotes Tags: #CityWalks #OpenMaps Format: bio block + pinned post + char counts
Example Output
1. Ledger. Indie map-maker weekly city walks; they/them; Lisbon user-stated. Handle @maps@example.social. Caps 160/500. Topics: walkable maps, transit, no politics. Link maps.example.com. Pin: Tuesday drop intro. Tags #CityWalks #OpenMaps. Forbidden: 10k, verified, ToS invent. 2. Bio (count). Indie city walking maps each Tuesday. they/them. Lisbon. Transit-friendly notes. No politics. [print N/160] 3. Fields. Website: https://maps.example.com only. 4. Pinned (<=500). Hello from @maps@example.social. Weekly walking map drops on Tuesday. Topics: walkable streets and transit notes. Site link once. Hashtags only allowed two. No politics. [print N/500] 5. Tags. #CityWalks #OpenMaps only. 6. Refuse. Follower flex, verified badge, engagement bait. 7. Alt. No image described; skip alt. 8. Compliance. Cut banned. Format bio+pin+counts. Gaps: avatar description NOT IN INPUTS. Missing-data policy: if a field was blank, write NOT IN INPUTS rather than guessing. Lock any tool version named in Inputs; if unnamed, write unknown. No invented testimonials, star ratings, or press logos. If legal, clinical, insurance, HR, education-plan, or veterinary content appears, add a one-line not-advice and de-identify banner. Quote banned-word hits and cut them. End with a gaps list of five bullets the user still owes you. Character and byte caps in the job are hard; print counts when relevant. Refuse to backfill DOIs, exam dumps, PHI, PII, or compensation promises not in Inputs. Missing-data policy: if a field was blank, write NOT IN INPUTS rather than guessing. Lock any tool version named in Inputs; if unnamed, write unknown. No invented testimonials, star ratings, or press logos. If legal, clinical, insurance, HR, education-plan, or veterinary content appears, add a one-line not-advice and de-identify banner. Quote banned-word hits and cut them. End with a gaps list of five bullets the user still owes you. Character and byte caps in the job are hard; print counts when relevant. Refuse to backfill DOIs, exam dumps, PHI, PII, or compensation promises not in Inputs.