#299 by GitHub stars
charlie947/social-media-skills
Turn a LinkedIn Analytics export into an interactive dark-themed React dashboard plus a written strategic analysis with 5 data-backed content recommendations. Reads every sheet in the export, builds charts for engagement trend, follower growth, post performance scatter, day-of-week heatmap, and audi
History
Review weekly changes to SKILL.md before updating. Dates mark the weeks in which we observed each version; checks apply to the recorded commits.
View weekly changes
skills/analytics-dashboard/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Local scripts
10ca79c0ec0b → 10ca79c0ec0b
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 10ca79c0ec0b
No earlier version was observed for comparison.
skills/content-matrix/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
10ca79c0ec0b → 10ca79c0ec0b
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 10ca79c0ec0b
No earlier version was observed for comparison.
skills/gemini-carousel/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
10ca79c0ec0b → 10ca79c0ec0b
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 10ca79c0ec0b
No earlier version was observed for comparison.
skills/gemini-infographic/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
10ca79c0ec0b → 10ca79c0ec0b
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 10ca79c0ec0b
No earlier version was observed for comparison.
skills/graphic-designer/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
10ca79c0ec0b → 10ca79c0ec0b
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 10ca79c0ec0b
No earlier version was observed for comparison.
skills/hook-generator/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
10ca79c0ec0b → 10ca79c0ec0b
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 10ca79c0ec0b
No earlier version was observed for comparison.
skills/newsletter-voice/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
10ca79c0ec0b → 10ca79c0ec0b
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 10ca79c0ec0b
No earlier version was observed for comparison.
skills/niche-research/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Local scripts
10ca79c0ec0b → 10ca79c0ec0b
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 10ca79c0ec0b
No earlier version was observed for comparison.
skills/pinned-comment/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
10ca79c0ec0b → 10ca79c0ec0b
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 10ca79c0ec0b
No earlier version was observed for comparison.
skills/post-formatter/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
10ca79c0ec0b → 10ca79c0ec0b
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 10ca79c0ec0b
No earlier version was observed for comparison.
skills/post-scorer/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
10ca79c0ec0b → 10ca79c0ec0b
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 10ca79c0ec0b
No earlier version was observed for comparison.
skills/post-writer/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
10ca79c0ec0b → 10ca79c0ec0b
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 10ca79c0ec0b
No earlier version was observed for comparison.
skills/profile-optimizer/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
10ca79c0ec0b → 10ca79c0ec0b
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 10ca79c0ec0b
No earlier version was observed for comparison.
skills/quote-post/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
10ca79c0ec0b → 10ca79c0ec0b
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 10ca79c0ec0b
No earlier version was observed for comparison.
skills/reels-scripting/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
10ca79c0ec0b → 10ca79c0ec0b
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 10ca79c0ec0b
No earlier version was observed for comparison.
skills/voice-builder/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Local scripts
10ca79c0ec0b → 10ca79c0ec0b
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 10ca79c0ec0b
No earlier version was observed for comparison.
skills/youtube-thumbnail/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
10ca79c0ec0b → 10ca79c0ec0b
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 10ca79c0ec0b
No earlier version was observed for comparison.
View on GitHubAdd to my skills
Verified commit 10ca79c0ec0be0f7654d19cd4f0c86b6fa6ed23b
git clone --filter=blob:none --no-checkout https://github.com/charlie947/social-media-skills.git .hotskills/charlie947-social-media-skills && git -C .hotskills/charlie947-social-media-skills checkout --detach 10ca79c0ec0be0f7654d19cd4f0c86b6fa6ed23b
# Copy each selected skill directory from .hotskills/charlie947-social-media-skills into .claude/skills/<skill-name>/4.6kGitHub stars
117stars in 7 days
17skills in this repository
4commits in 30 days
Heat
6.7- Star growth, last 7 daysAhead of 93% of tracked repositories
- Star growth, last 24 hoursAhead of 93% of tracked repositories
- Rank movement, last 7 daysAhead of 36% of tracked repositories
- Commits, last 30 daysAhead of 67% of tracked repositories
- Accounts asking about it through MCP, last 7 daysNot available
- Hot votes this weekAhead of 0% of tracked repositories
Heat never changes the order by stars, and sponsorship never touches it. How heat works
Stars over time
Individual skills in this repository
- analytics-dashboard
skills/analytics-dashboard - content-matrix
skills/content-matrix - gemini-carousel
skills/gemini-carousel - gemini-infographic
skills/gemini-infographic - graphic-designer
skills/graphic-designer - hook-generator
skills/hook-generator - newsletter-voice
skills/newsletter-voice - niche-research
skills/niche-research - pinned-comment
skills/pinned-comment - post-formatter
skills/post-formatter - post-scorer
skills/post-scorer - post-writer
skills/post-writer - profile-optimizer
skills/profile-optimizer - quote-post
skills/quote-post - reels-scripting
skills/reels-scripting - voice-builder
skills/voice-builder - youtube-thumbnail
skills/youtube-thumbnail
How it works
analytics-dashboard
When your agent uses it
Turn a LinkedIn Analytics export into an interactive dark-themed React dashboard plus a written strategic analysis with 5 data-backed content recommendations. Reads every sheet in the export, builds charts for engagement trend, follower growth, post performance scatter, day-of-week heatmap, and audience breakdown. Use this skill whenever the user says "analyse my linkedin", "linkedin analytics", "build my dashboard", "review my performance", or uploads a LinkedIn Analytics export file. Requires the user's LinkedIn Analytics export (xlsx) as input.
What it loads into context
Frontmatter
113 tokensAlways available to the agent
SKILL.md
1,553 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Codex and Claude runtime
- CRITICAL: Auto-start on load
- Step 1. Get the export file
- Step 2. Parse the data
- Step 3. Build the interactive dashboard
- Step 4. Written strategic analysis
- Step 5. Offer the next move
- Rules
Files
../../.claude-plugin/marketplace.jsonasset789 bytesSKILL.mdcore7,383 bytesSKILL.mdcore7,383 bytesSKILL.mdcore7,383 bytesSKILL.mdcore7,383 bytesSKILL.mdcore7,383 bytesSKILL.mdcore7,383 bytes
Read SKILL.md
# Analytics Dashboard
## Codex and Claude runtime
- Use this skill in Codex or Claude with the tools actually available in the current task. `AskUserQuestion` examples describe the questions, not a required API: use an available question tool within its limits, or ask in chat. Reuse answers and source material already supplied.
- Work in the user-selected project. Read its `about-me.md`, `voice.md` and relevant brand files before personalised work. Confirm the intended author if files conflict or contain starter defaults. Ask for missing facts or run `voice-builder`; never inherit the maintainer's identity, accounts or private files.
- Resolve bundled `references/` relative to this skill folder. For an explicitly requested profile refresh, read and update the canonical `about-me.md`, `voice.md` or `newsletter-voice.md` in place, preserving unrelated user facts and rules. Consumers must reread those canonical files. Use a new filename only for new deliverables that would collide with unrelated existing files. Installation alone never starts an interview or writes files. Do not write persistent learnings unless requested.
- Use supplied evidence first. Verify external claims through available search/source tools when needed. If a source or integration is unavailable, name the missing capability and offer supplied text/export input. Never invent facts, first-person experience, metrics or a successful tool run.
- Connect only services needed for the chosen route through the user's existing account. Never print credentials or overwrite connections. Drafting, saving and reviewing do not authorise publishing, sending messages or changing accounts.
## CRITICAL: Auto-start on load
When this skill triggers, go straight to Step 1.
content-matrix
When your agent uses it
Generate 24 to 40 LinkedIn post ideas in a single table by pairing the user's content pillars with 8 proven content formats. Based on the Justin Welsh content matrix. Use this skill whenever the user says "give me post ideas", "content matrix", "what should I post about", "generate post ideas", "content ideation", or "map out my content for the month". Pulls from about-me.md and voice.md if they exist, otherwise asks for pillars and context.
What it loads into context
Frontmatter
109 tokensAlways available to the agent
SKILL.md
1,458 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Codex and Claude runtime
- CRITICAL: Auto-start on load
- Step 1. Gather inputs
- Step 2. Build the matrix
- Step 3. Output (surface-aware)
- Step 4. Offer the next move
- Rules
Files
SKILL.mdcore6,466 bytesSKILL.mdcore6,466 bytesSKILL.mdcore6,466 bytesSKILL.mdcore6,466 bytes
Read SKILL.md
# Content Matrix
## Codex and Claude runtime
- Use this skill in Codex or Claude with the tools actually available in the current task. `AskUserQuestion` examples describe the questions, not a required API: use an available question tool within its limits, or ask in chat. Reuse answers and source material already supplied.
- Work in the user-selected project. Read its `about-me.md`, `voice.md` and relevant brand files before personalised work. Confirm the intended author if files conflict or contain starter defaults. Ask for missing facts or run `voice-builder`; never inherit the maintainer's identity, accounts or private files.
- Resolve bundled `references/` relative to this skill folder. For an explicitly requested profile refresh, read and update the canonical `about-me.md`, `voice.md` or `newsletter-voice.md` in place, preserving unrelated user facts and rules. Consumers must reread those canonical files. Use a new filename only for new deliverables that would collide with unrelated existing files. Installation alone never starts an interview or writes files. Do not write persistent learnings unless requested.
- Use supplied evidence first. Verify external claims through available search/source tools when needed. If a source or integration is unavailable, name the missing capability and offer supplied text/export input. Never invent facts, first-person experience, metrics or a successful tool run.
- Connect only services needed for the chosen route through the user's existing account. Never print credentials or overwrite connections. Drafting, saving and reviewing do not authorise publishing, sending messages or changing accounts.
## CRITICAL: Auto-start on load
When this skill triggers, go straight to Step 1. Do not summarise. Start input gathering immediately.
gemini-carousel
When your agent uses it
Generate a branded slide-by-slide LinkedIn carousel using Gemini. Takes source content, builds a design brief, waits for approval, then outputs per-slide image generation prompts. 1080x1350 vertical format. Use this skill whenever the user says "carousel", "build a carousel", "turn this into a carousel", "gemini carousel", or wants multi-slide LinkedIn content. Always includes an approval gate between brief and image generation.
What it loads into context
Frontmatter
98 tokensAlways available to the agent
SKILL.md
1,457 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Codex and Claude runtime
- Visual completion state
- CRITICAL: Auto-start on load
- Step 1. Gather inputs
- Step 2. Build the design brief
- Step 3. Output per-slide prompts
- Step 4. Offer one-shot alternative
- Rules
Files
SKILL.mdcore6,733 bytesSKILL.mdcore6,733 bytesSKILL.mdcore6,733 bytesSKILL.mdcore6,733 bytesSKILL.mdcore6,733 bytesSKILL.mdcore6,733 bytes
Read SKILL.md
# Gemini Carousel
## Codex and Claude runtime
- Use this skill in Codex or Claude with the tools actually available in the current task. `AskUserQuestion` examples describe the questions, not a required API: use an available question tool within its limits, or ask in chat. Reuse answers and source material already supplied.
- Work in the user-selected project. Read its `about-me.md`, `voice.md` and relevant brand files before personalised work. Confirm the intended author if files conflict or contain starter defaults. Ask for missing facts or run `voice-builder`; never inherit the maintainer's identity, accounts or private files.
- Resolve bundled `references/` relative to this skill folder. For an explicitly requested profile refresh, read and update the canonical `about-me.md`, `voice.md` or `newsletter-voice.md` in place, preserving unrelated user facts and rules. Consumers must reread those canonical files. Use a new filename only for new deliverables that would collide with unrelated existing files. Installation alone never starts an interview or writes files. Do not write persistent learnings unless requested.
- Use supplied evidence first. Verify external claims through available search/source tools when needed. If a source or integration is unavailable, name the missing capability and offer supplied text/export input. Never invent facts, first-person experience, metrics or a successful tool run.
- Connect only services needed for the chosen route through the user's existing account. Never print credentials or overwrite connections. Drafting, saving and reviewing do not authorise publishing, sending messages or changing accounts.
## Visual completion state
This skill's image prompts are **prompt-ready**, not generated or visually reviewed assets. Keep its named Gemini workflow unless the user requests another generator. A missing image service does not block writing a prompt. When images are supplied or generated, open and inspect each export at full size and feed size (about 360px wide, 320px for thumbnails). Check exact copy, dimensions, clipping, legibility, brand colours, font appearance, logos and reference fidelity. Fix and re-inspect failed exports. Record any unavailable export or inspection as pending. An image prompt or raster export is not an editable design file.
gemini-infographic
When your agent uses it
Generate a hand-drawn whiteboard infographic prompt. Takes source content (a post, newsletter, blog, research note) and returns a complete Gemini image generation prompt with a structured brief. Use this skill whenever the user says "whiteboard infographic", "gemini infographic", "hand-drawn graphic", "turn this into a whiteboard", or wants an AI-generated infographic for a post.
What it loads into context
Frontmatter
89 tokensAlways available to the agent
SKILL.md
1,294 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Codex and Claude runtime
- Visual completion state
- CRITICAL: Auto-start on load
- Step 1. Get the source content
- Step 2. Build the brief
- Step 3. Output the Gemini prompt
- Step 4. Offer iteration
- Rules
Files
SKILL.mdcore6,158 bytesSKILL.mdcore6,158 bytesSKILL.mdcore6,158 bytesSKILL.mdcore6,158 bytesSKILL.mdcore6,158 bytesSKILL.mdcore6,158 bytes
Read SKILL.md
# Gemini Infographic
## Codex and Claude runtime
- Use this skill in Codex or Claude with the tools actually available in the current task. `AskUserQuestion` examples describe the questions, not a required API: use an available question tool within its limits, or ask in chat. Reuse answers and source material already supplied.
- Work in the user-selected project. Read its `about-me.md`, `voice.md` and relevant brand files before personalised work. Confirm the intended author if files conflict or contain starter defaults. Ask for missing facts or run `voice-builder`; never inherit the maintainer's identity, accounts or private files.
- Resolve bundled `references/` relative to this skill folder. For an explicitly requested profile refresh, read and update the canonical `about-me.md`, `voice.md` or `newsletter-voice.md` in place, preserving unrelated user facts and rules. Consumers must reread those canonical files. Use a new filename only for new deliverables that would collide with unrelated existing files. Installation alone never starts an interview or writes files. Do not write persistent learnings unless requested.
- Use supplied evidence first. Verify external claims through available search/source tools when needed. If a source or integration is unavailable, name the missing capability and offer supplied text/export input. Never invent facts, first-person experience, metrics or a successful tool run.
- Connect only services needed for the chosen route through the user's existing account. Never print credentials or overwrite connections. Drafting, saving and reviewing do not authorise publishing, sending messages or changing accounts.
## Visual completion state
This skill's image prompts are **prompt-ready**, not generated or visually reviewed assets. Keep its named Gemini workflow unless the user requests another generator. A missing image service does not block writing a prompt. When images are supplied or generated, open and inspect each export at full size and feed size (about 360px wide, 320px for thumbnails). Check exact copy, dimensions, clipping, legibility, brand colours, font appearance, logos and reference fidelity. Fix and re-inspect failed exports. Record any unavailable export or inspection as pending. An image prompt or raster export is not an editable design file.
graphic-designer
When your agent uses it
Create LinkedIn post graphics. Decides between an HTML/CSS structured graphic or an AI-generated infographic based on the post content. Use this skill whenever the user says "design a graphic", "create a visual", "make an image", "graphic for my post", "LinkedIn image", or wants any visual content to pair with a LinkedIn post. Also trigger when the user finishes writing a post and wants a matching graphic.
What it loads into context
Frontmatter
97 tokensAlways available to the agent
SKILL.md
2,132 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Codex and Claude runtime
- Visual completion state
- CRITICAL: Auto-start on load
- Step 1. Read the post
- Path A: HTML/CSS structured graphic
- Path B: Image generation prompt
- After either path
- Rules
Files
SKILL.mdcore9,917 bytesSKILL.mdcore9,917 bytesSKILL.mdcore9,917 bytesSKILL.mdcore9,917 bytes
Read SKILL.md
# Graphic Designer
## Codex and Claude runtime
- Use this skill in Codex or Claude with the tools actually available in the current task. `AskUserQuestion` examples describe the questions, not a required API: use an available question tool within its limits, or ask in chat. Reuse answers and source material already supplied.
- Work in the user-selected project. Read its `about-me.md`, `voice.md` and relevant brand files before personalised work. Confirm the intended author if files conflict or contain starter defaults. Ask for missing facts or run `voice-builder`; never inherit the maintainer's identity, accounts or private files.
- Resolve bundled `references/` relative to this skill folder. For an explicitly requested profile refresh, read and update the canonical `about-me.md`, `voice.md` or `newsletter-voice.md` in place, preserving unrelated user facts and rules. Consumers must reread those canonical files. Use a new filename only for new deliverables that would collide with unrelated existing files. Installation alone never starts an interview or writes files. Do not write persistent learnings unless requested.
- Use supplied evidence first. Verify external claims through available search/source tools when needed. If a source or integration is unavailable, name the missing capability and offer supplied text/export input. Never invent facts, first-person experience, metrics or a successful tool run.
- Connect only services needed for the chosen route through the user's existing account. Never print credentials or overwrite connections. Drafting, saving and reviewing do not authorise publishing, sending messages or changing accounts.
## Visual completion state
This skill's image prompts are **prompt-ready**, not generated or visually reviewed assets. Keep its named Gemini workflow unless the user requests another generator. A missing image service does not block writing a prompt. When images are supplied or generated, open and inspect each export at full size and feed size (about 360px wide, 320px for thumbnails). Check exact copy, dimensions, clipping, legibility, brand colours, font appearance, logos and reference fidelity. Fix and re-inspect failed exports. Record any unavailable export or inspection as pending. An image prompt or raster export is not an editable design file.
hook-generator
When your agent uses it
Generate 6 clickbait-style LinkedIn hook variations for any topic. Two-line hooks built on the formula: a 40-char opening line, a 40-char bold contrast line. Uses supplied numbers and genuine first-person experience when available. Use this skill whenever the user says "write me hooks", "hook ideas", "generate hooks", "I need a hook for a post about...", or pastes a topic and asks for openers. Fast output, no preamble.
What it loads into context
Frontmatter
105 tokensAlways available to the agent
SKILL.md
973 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Codex and Claude runtime
- CRITICAL: Auto-start on load
- Step 1. Get the topic
- Step 2. Write 6 hook variations
- Step 3. Output format
- Step 4. Offer the next move
- Rules
Files
SKILL.mdcore4,267 bytesSKILL.mdcore4,267 bytesSKILL.mdcore4,267 bytesSKILL.mdcore4,267 bytes
Read SKILL.md
# Hook Generator
## Codex and Claude runtime
- Use this skill in Codex or Claude with the tools actually available in the current task. `AskUserQuestion` examples describe the questions, not a required API: use an available question tool within its limits, or ask in chat. Reuse answers and source material already supplied.
- Work in the user-selected project. Read its `about-me.md`, `voice.md` and relevant brand files before personalised work. Confirm the intended author if files conflict or contain starter defaults. Ask for missing facts or run `voice-builder`; never inherit the maintainer's identity, accounts or private files.
- Resolve bundled `references/` relative to this skill folder. For an explicitly requested profile refresh, read and update the canonical `about-me.md`, `voice.md` or `newsletter-voice.md` in place, preserving unrelated user facts and rules. Consumers must reread those canonical files. Use a new filename only for new deliverables that would collide with unrelated existing files. Installation alone never starts an interview or writes files. Do not write persistent learnings unless requested.
- Use supplied evidence first. Verify external claims through available search/source tools when needed. If a source or integration is unavailable, name the missing capability and offer supplied text/export input. Never invent facts, first-person experience, metrics or a successful tool run.
- Connect only services needed for the chosen route through the user's existing account. Never print credentials or overwrite connections. Drafting, saving and reviewing do not authorise publishing, sending messages or changing accounts.
## CRITICAL: Auto-start on load
When this skill triggers, go straight to Step 1. Do not summarise. Do not explain what makes a good hook.
newsletter-voice
When your agent uses it
Build newsletter writing instructions inside a Codex or Claude project. Runs after voice-builder. Produces newsletter-voice.md, a single file the assistant references when drafting newsletters in the user's voice. Works with or without existing newsletter samples: if the user has past issues, the skill analyses them; if not, the skill offers 6 archetypes tuned to the user's voice. Trigger whenever the user says "build my newsletter voice", "learn my newsletter style", "set up my newsletter system", "train on my newsletters", "newsletter onboarding", or drops newsletter samples into chat asking for an analysis. Requires voice-builder to have run first: the skill needs voice.md and about-me.md in the project to work.
What it loads into context
Frontmatter
152 tokensAlways available to the agent
SKILL.md
2,138 tokensWhen the skill is activated
Reference documents
1,832 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Codex and Claude runtime
- Prerequisites check
- Step 1. Check for samples
- Step 2a. Sample-based analysis
- Step 2b. Archetype selection
- Step 3. Write newsletter-voice.md
- Step 4. Confirm and hand off
- What this skill produces
- Rules
Files
SKILL.mdcore9,853 bytesSKILL.mdcore9,853 bytesSKILL.mdcore9,853 bytesSKILL.mdcore9,853 bytesreferences/archetypes.mddoc7,652 bytes
Read SKILL.md
# Newsletter Voice
## Codex and Claude runtime
- Use this skill in Codex or Claude with the tools actually available in the current task. `AskUserQuestion` examples describe the questions, not a required API: use an available question tool within its limits, or ask in chat. Reuse answers and source material already supplied.
- Work in the user-selected project. Read its `about-me.md`, `voice.md` and relevant brand files before personalised work. Confirm the intended author if files conflict or contain starter defaults. Ask for missing facts or run `voice-builder`; never inherit the maintainer's identity, accounts or private files.
- Resolve bundled `references/` relative to this skill folder. For an explicitly requested profile refresh, read and update the canonical `about-me.md`, `voice.md` or `newsletter-voice.md` in place, preserving unrelated user facts and rules. Consumers must reread those canonical files. Use a new filename only for new deliverables that would collide with unrelated existing files. Installation alone never starts an interview or writes files. Do not write persistent learnings unless requested.
- Use supplied evidence first. Verify external claims through available search/source tools when needed. If a source or integration is unavailable, name the missing capability and offer supplied text/export input. Never invent facts, first-person experience, metrics or a successful tool run.
- Connect only services needed for the chosen route through the user's existing account. Never print credentials or overwrite connections. Drafting, saving and reviewing do not authorise publishing, sending messages or changing accounts.
## Prerequisites check
The moment this skill is triggered, check the project root for voice.md and about-me.md.
niche-research
When your agent uses it
Surface the 20 most relevant stories in a niche from the last 7 days using available live research tools. Verified dates, real links, shareable angles. Use available browser or web search tools to inspect dated source material. Use this skill whenever the user says "research my niche", "what's trending", "find stories", "this week's news", "content research", or drops a niche and asks what's happening in it. Requires live source access for current research.
What it loads into context
Frontmatter
104 tokensAlways available to the agent
SKILL.md
1,482 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Codex and Claude runtime
- CRITICAL: Auto-start on load
- Prerequisites
- Step 1. Gather the niche
- Step 2. Browse like a human researcher
- Step 3. Synthesise into themes
- Step 4. Output
- Step 5. Offer the next move
- Rules
Files
SKILL.mdcore6,846 bytesSKILL.mdcore6,846 bytesSKILL.mdcore6,846 bytesSKILL.mdcore6,846 bytesSKILL.mdcore6,846 bytesSKILL.mdcore6,846 bytesSKILL.mdcore6,846 bytes
Read SKILL.md
# Niche Research
## Codex and Claude runtime
- Use this skill in Codex or Claude with the tools actually available in the current task. `AskUserQuestion` examples describe the questions, not a required API: use an available question tool within its limits, or ask in chat. Reuse answers and source material already supplied.
- Work in the user-selected project. Read its `about-me.md`, `voice.md` and relevant brand files before personalised work. Confirm the intended author if files conflict or contain starter defaults. Ask for missing facts or run `voice-builder`; never inherit the maintainer's identity, accounts or private files.
- Resolve bundled `references/` relative to this skill folder. For an explicitly requested profile refresh, read and update the canonical `about-me.md`, `voice.md` or `newsletter-voice.md` in place, preserving unrelated user facts and rules. Consumers must reread those canonical files. Use a new filename only for new deliverables that would collide with unrelated existing files. Installation alone never starts an interview or writes files. Do not write persistent learnings unless requested.
- Use supplied evidence first. Verify external claims through available search/source tools when needed. If a source or integration is unavailable, name the missing capability and offer supplied text/export input. Never invent facts, first-person experience, metrics or a successful tool run.
- Connect only services needed for the chosen route through the user's existing account. Never print credentials or overwrite connections. Drafting, saving and reviewing do not authorise publishing, sending messages or changing accounts.
## CRITICAL: Auto-start on load
When this skill triggers, go straight to Step 1. Do not summarise the research method.
pinned-comment
When your agent uses it
Write deadpan LinkedIn pinned comments AND matching image generation prompts in the user’s voice. Use when the user asks for a pinned comment, pin comment, or first comment for a LinkedIn post. ALWAYS produce the image prompt FIRST, then caption it with the 4-line comment. Output both together unless told otherwise.
What it loads into context
Frontmatter
71 tokensAlways available to the agent
SKILL.md
2,034 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Codex and Claude runtime
- Visual completion state
- Why This Skill Exists
- The Core Insight (read this first)
- THE PROCESS (follow in order)
- THE 4-LINE RULES (non-negotiable)
- GOLD STANDARD EXAMPLE
- OTHER IMAGE GAG PATTERNS (for reference)
- WHAT TO AVOID
- OUTPUT FORMAT
Files
SKILL.mdcore9,123 bytesSKILL.mdcore9,123 bytesSKILL.mdcore9,123 bytesSKILL.mdcore9,123 bytes
Read SKILL.md
# LinkedIn Pinned Comment + Image Prompt Skill
## Codex and Claude runtime
- Use this skill in Codex or Claude with the tools actually available in the current task. `AskUserQuestion` examples describe the questions, not a required API: use an available question tool within its limits, or ask in chat. Reuse answers and source material already supplied.
- Work in the user-selected project. Read its `about-me.md`, `voice.md` and relevant brand files before personalised work. Confirm the intended author if files conflict or contain starter defaults. Ask for missing facts or run `voice-builder`; never inherit the maintainer's identity, accounts or private files.
- Resolve bundled `references/` relative to this skill folder. For an explicitly requested profile refresh, read and update the canonical `about-me.md`, `voice.md` or `newsletter-voice.md` in place, preserving unrelated user facts and rules. Consumers must reread those canonical files. Use a new filename only for new deliverables that would collide with unrelated existing files. Installation alone never starts an interview or writes files. Do not write persistent learnings unless requested.
- Use supplied evidence first. Verify external claims through available search/source tools when needed. If a source or integration is unavailable, name the missing capability and offer supplied text/export input. Never invent facts, first-person experience, metrics or a successful tool run.
- Connect only services needed for the chosen route through the user's existing account. Never print credentials or overwrite connections. Drafting, saving and reviewing do not authorise publishing, sending messages or changing accounts.
## Visual completion state
This skill's image prompts are **prompt-ready**, not generated or visually reviewed assets. Keep its named Gemini workflow unless the user requests another generator. A missing image service does not block writing a prompt. When images are supplied or generated, open and inspect each export at full size and feed size (about 360px wide, 320px for thumbnails). Check exact copy, dimensions, clipping, legibility, brand colours, font appearance, logos and reference fidelity. Fix and re-inspect failed exports. Record any unavailable export or inspection as pending. An image prompt or raster export is not an editable design file.
post-formatter
When your agent uses it
Turn a topic into a ready-to-publish LinkedIn post using PAS, AIDA, BAB, STAR, or SLAY frameworks. Up to 20 nonblank lines, mobile-formatted with blank lines between sentences. Use this skill whenever the user says "format this as a post", "turn this into a LinkedIn post", "write it as PAS" or any named framework, or wants a properly structured post from a topic. Different from post-writer: post-formatter applies a strict framework. post-writer drafts in the user's voice without framework constraints.
What it loads into context
Frontmatter
124 tokensAlways available to the agent
SKILL.md
1,323 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Codex and Claude runtime
- CRITICAL: Auto-start on load
- Step 1. Gather inputs
- Step 2. Write the post
- Step 3. Structure
- Step 4. Output
- Step 5. Offer the next move
- Rules
Files
SKILL.mdcore5,708 bytesSKILL.mdcore5,708 bytesSKILL.mdcore5,708 bytesSKILL.mdcore5,708 bytes
Read SKILL.md
# Post Formatter
## Codex and Claude runtime
- Use this skill in Codex or Claude with the tools actually available in the current task. `AskUserQuestion` examples describe the questions, not a required API: use an available question tool within its limits, or ask in chat. Reuse answers and source material already supplied.
- Work in the user-selected project. Read its `about-me.md`, `voice.md` and relevant brand files before personalised work. Confirm the intended author if files conflict or contain starter defaults. Ask for missing facts or run `voice-builder`; never inherit the maintainer's identity, accounts or private files.
- Resolve bundled `references/` relative to this skill folder. For an explicitly requested profile refresh, read and update the canonical `about-me.md`, `voice.md` or `newsletter-voice.md` in place, preserving unrelated user facts and rules. Consumers must reread those canonical files. Use a new filename only for new deliverables that would collide with unrelated existing files. Installation alone never starts an interview or writes files. Do not write persistent learnings unless requested.
- Use supplied evidence first. Verify external claims through available search/source tools when needed. If a source or integration is unavailable, name the missing capability and offer supplied text/export input. Never invent facts, first-person experience, metrics or a successful tool run.
- Connect only services needed for the chosen route through the user's existing account. Never print credentials or overwrite connections. Drafting, saving and reviewing do not authorise publishing, sending messages or changing accounts.
## CRITICAL: Auto-start on load
When this skill triggers, go straight to Step 1. Do not summarise. Start input gathering immediately.
post-scorer
When your agent uses it
Score a LinkedIn post using real performance data. Pulls the user's own post history via Apify (or uses cached data) to identify what actually performs, then scores the draft against those patterns. Use this skill whenever the user says "score my post", "review my post", "rate this post", "give me feedback", "how good is this post", or pastes a LinkedIn post and asks for critique. Separates historical comparisons from an explicitly labelled editorial-only fallback. Designed for live scoring at events and everyday post review.
What it loads into context
Frontmatter
120 tokensAlways available to the agent
SKILL.md
2,020 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Codex and Claude runtime
- CRITICAL: Auto-start on load
- Step 1. Get the post
- Step 2. Load scoring data
- Step 3. Analyse the top performers
- Step 4. Score the post
- Step 5. Output the scorecard
- Step 6. Offer next steps
- Rules
Files
SKILL.mdcore9,503 bytesSKILL.mdcore9,503 bytesSKILL.mdcore9,503 bytesSKILL.mdcore9,503 bytes
Read SKILL.md
# Post Scorer
## Codex and Claude runtime
- Use this skill in Codex or Claude with the tools actually available in the current task. `AskUserQuestion` examples describe the questions, not a required API: use an available question tool within its limits, or ask in chat. Reuse answers and source material already supplied.
- Work in the user-selected project. Read its `about-me.md`, `voice.md` and relevant brand files before personalised work. Confirm the intended author if files conflict or contain starter defaults. Ask for missing facts or run `voice-builder`; never inherit the maintainer's identity, accounts or private files.
- Resolve bundled `references/` relative to this skill folder. For an explicitly requested profile refresh, read and update the canonical `about-me.md`, `voice.md` or `newsletter-voice.md` in place, preserving unrelated user facts and rules. Consumers must reread those canonical files. Use a new filename only for new deliverables that would collide with unrelated existing files. Installation alone never starts an interview or writes files. Do not write persistent learnings unless requested.
- Use supplied evidence first. Verify external claims through available search/source tools when needed. If a source or integration is unavailable, name the missing capability and offer supplied text/export input. Never invent facts, first-person experience, metrics or a successful tool run.
- Connect only services needed for the chosen route through the user's existing account. Never print credentials or overwrite connections. Drafting, saving and reviewing do not authorise publishing, sending messages or changing accounts.
## CRITICAL: Auto-start on load
When this skill triggers, go straight to Step 1. Do not summarise. Do not explain the scoring method. Start immediately.
post-writer
When your agent uses it
Write LinkedIn posts that match the user's voice system (about-me.md and voice.md). Use this skill whenever the user says "write a post", "draft a post", "LinkedIn post", "post about [topic]", "content idea", or wants help writing any LinkedIn content. Also trigger when the user pastes a context dump (notes, transcripts, bullet points) and wants it turned into a post. Always references the voice files in the project before writing. Always outputs the final post in a code block.
What it loads into context
Frontmatter
116 tokensAlways available to the agent
SKILL.md
1,719 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Codex and Claude runtime
- CRITICAL: Auto-start on load
- Step 1. Gather inputs
- Step 2. Research and plan
- Step 3. Write the draft
- Step 4. Iterate
- Rules
Files
SKILL.mdcore7,832 bytesSKILL.mdcore7,832 bytesSKILL.mdcore7,832 bytesSKILL.mdcore7,832 bytesSKILL.mdcore7,832 bytes
Read SKILL.md
# Post Writer
## Codex and Claude runtime
- Use this skill in Codex or Claude with the tools actually available in the current task. `AskUserQuestion` examples describe the questions, not a required API: use an available question tool within its limits, or ask in chat. Reuse answers and source material already supplied.
- Work in the user-selected project. Read its `about-me.md`, `voice.md` and relevant brand files before personalised work. Confirm the intended author if files conflict or contain starter defaults. Ask for missing facts or run `voice-builder`; never inherit the maintainer's identity, accounts or private files.
- Resolve bundled `references/` relative to this skill folder. For an explicitly requested profile refresh, read and update the canonical `about-me.md`, `voice.md` or `newsletter-voice.md` in place, preserving unrelated user facts and rules. Consumers must reread those canonical files. Use a new filename only for new deliverables that would collide with unrelated existing files. Installation alone never starts an interview or writes files. Do not write persistent learnings unless requested.
- Use supplied evidence first. Verify external claims through available search/source tools when needed. If a source or integration is unavailable, name the missing capability and offer supplied text/export input. Never invent facts, first-person experience, metrics or a successful tool run.
- Connect only services needed for the chosen route through the user's existing account. Never print credentials or overwrite connections. Drafting, saving and reviewing do not authorise publishing, sending messages or changing accounts.
## CRITICAL: Auto-start on load
The moment this skill triggers, go straight to Step 1. Do not summarise the skill. Do not explain what it does. Do not list the files it references. Jump to input gathering immediately.
profile-optimizer
When your agent uses it
Rebuild a LinkedIn profile for maximum conversions. Produces new headline options, about section, experience section, featured section strategy, and 4 image generation prompts (banner, profile picture, 2 featured tiles). Use this skill whenever the user says "optimize my profile", "fix my LinkedIn", "rewrite my headline", "profile review", "LinkedIn audit", "rebuild my profile", or wants help with any part of their LinkedIn profile. Also trigger when the user uploads a LinkedIn profile PDF or screenshot for review.
What it loads into context
Frontmatter
120 tokensAlways available to the agent
SKILL.md
2,636 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Codex and Claude runtime
- Visual completion state
- CRITICAL: Auto-start on load
- Step 1. Gather inputs
- Step 2. The Headline
- Step 3. The About Section
- Step 4. The Experience Section
- Step 5. Featured Section Strategy
- Step 6. Visual Design Brief
- Rules
Files
SKILL.mdcore11,565 bytesSKILL.mdcore11,565 bytesSKILL.mdcore11,565 bytesSKILL.mdcore11,565 bytes
Read SKILL.md
# Profile Optimizer
## Codex and Claude runtime
- Use this skill in Codex or Claude with the tools actually available in the current task. `AskUserQuestion` examples describe the questions, not a required API: use an available question tool within its limits, or ask in chat. Reuse answers and source material already supplied.
- Work in the user-selected project. Read its `about-me.md`, `voice.md` and relevant brand files before personalised work. Confirm the intended author if files conflict or contain starter defaults. Ask for missing facts or run `voice-builder`; never inherit the maintainer's identity, accounts or private files.
- Resolve bundled `references/` relative to this skill folder. For an explicitly requested profile refresh, read and update the canonical `about-me.md`, `voice.md` or `newsletter-voice.md` in place, preserving unrelated user facts and rules. Consumers must reread those canonical files. Use a new filename only for new deliverables that would collide with unrelated existing files. Installation alone never starts an interview or writes files. Do not write persistent learnings unless requested.
- Use supplied evidence first. Verify external claims through available search/source tools when needed. If a source or integration is unavailable, name the missing capability and offer supplied text/export input. Never invent facts, first-person experience, metrics or a successful tool run.
- Connect only services needed for the chosen route through the user's existing account. Never print credentials or overwrite connections. Drafting, saving and reviewing do not authorise publishing, sending messages or changing accounts.
## Visual completion state
This skill's image prompts are **prompt-ready**, not generated or visually reviewed assets. Keep its named Gemini workflow unless the user requests another generator. A missing image service does not block writing a prompt. When images are supplied or generated, open and inspect each export at full size and feed size (about 360px wide, 320px for thumbnails). Check exact copy, dimensions, clipping, legibility, brand colours, font appearance, logos and reference fidelity. Fix and re-inspect failed exports. Record any unavailable export or inspection as pending. An image prompt or raster export is not an editable design file.
quote-post
When your agent uses it
Two-step workflow for creating quote posts on LinkedIn. The assistant drafts original short quotes to accompany a caption, then produces a Gemini prompt that recreates a reference image with the chosen quote baked in. Use this skill whenever the user says "quote post", "quote graphic", "motivational post", "build me a quote", or wants a low-effort high-engagement LinkedIn graphic. Optimised for LinkedIn's employee and early-career audience, which skews toward motivational content.
What it loads into context
Frontmatter
108 tokensAlways available to the agent
SKILL.md
1,373 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Codex and Claude runtime
- Visual completion state
- CRITICAL: Auto-start on load
- Step 1. Get the caption
- Step 2. Generate quote options
- Step 3. Get the reference image
- Step 4. Output the Gemini prompt
- Step 5. Honest expectation-setting
- Rules
Files
SKILL.mdcore6,323 bytesSKILL.mdcore6,323 bytesSKILL.mdcore6,323 bytesSKILL.mdcore6,323 bytes
Read SKILL.md
# Quote Post
## Codex and Claude runtime
- Use this skill in Codex or Claude with the tools actually available in the current task. `AskUserQuestion` examples describe the questions, not a required API: use an available question tool within its limits, or ask in chat. Reuse answers and source material already supplied.
- Work in the user-selected project. Read its `about-me.md`, `voice.md` and relevant brand files before personalised work. Confirm the intended author if files conflict or contain starter defaults. Ask for missing facts or run `voice-builder`; never inherit the maintainer's identity, accounts or private files.
- Resolve bundled `references/` relative to this skill folder. For an explicitly requested profile refresh, read and update the canonical `about-me.md`, `voice.md` or `newsletter-voice.md` in place, preserving unrelated user facts and rules. Consumers must reread those canonical files. Use a new filename only for new deliverables that would collide with unrelated existing files. Installation alone never starts an interview or writes files. Do not write persistent learnings unless requested.
- Use supplied evidence first. Verify external claims through available search/source tools when needed. If a source or integration is unavailable, name the missing capability and offer supplied text/export input. Never invent facts, first-person experience, metrics or a successful tool run.
- Connect only services needed for the chosen route through the user's existing account. Never print credentials or overwrite connections. Drafting, saving and reviewing do not authorise publishing, sending messages or changing accounts.
## Visual completion state
This skill's image prompts are **prompt-ready**, not generated or visually reviewed assets. Keep its named Gemini workflow unless the user requests another generator. A missing image service does not block writing a prompt. When images are supplied or generated, open and inspect each export at full size and feed size (about 360px wide, 320px for thumbnails). Check exact copy, dimensions, clipping, legibility, brand colours, font appearance, logos and reference fidelity. Fix and re-inspect failed exports. Record any unavailable export or inspection as pending. An image prompt or raster export is not an editable design file.
reels-scripting
When your agent uses it
Turn a reference Instagram Reel into a script for your own Reel, tuned to your voice and repurposed from your newsletter content. Takes a Reel URL or Notion reference link, uses Apify to scrape the video, sends it to Gemini 2.5 Flash for full transcript + hook + structure analysis, then writes a new script applying the same patterns to your newsletter topic. Use this skill whenever the user says "script a reel", "reels scripting", "turn this into a reel", pastes an Instagram Reel URL, or references their Notion outlier reels database. The URL-to-video-analysis route needs APIFY_API_TOKEN and GOOGLE_AI_API_KEY; supplied input can skip the corresponding stages.
What it loads into context
Frontmatter
152 tokensAlways available to the agent
SKILL.md
2,292 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Codex and Claude runtime
- CRITICAL: Auto-start on load
- Prerequisites
- Step 1. Get the reference
- Step 2. Get the newsletter topic
- Step 3. Scrape and download the Reel
- Step 4. Analyse with Gemini 2.5 Flash
- Step 5. Write the new Reel script
- Step 6. QA loop
- Step 7. Hand off the script
- Rules
Files
SKILL.mdcore10,344 bytesSKILL.mdcore10,344 bytesSKILL.mdcore10,344 bytesSKILL.mdcore10,344 bytesSKILL.mdcore10,344 bytes
Read SKILL.md
# Reels Scripting
## Codex and Claude runtime
- Use this skill in Codex or Claude with the tools actually available in the current task. `AskUserQuestion` examples describe the questions, not a required API: use an available question tool within its limits, or ask in chat. Reuse answers and source material already supplied.
- Work in the user-selected project. Read its `about-me.md`, `voice.md` and relevant brand files before personalised work. Confirm the intended author if files conflict or contain starter defaults. Ask for missing facts or run `voice-builder`; never inherit the maintainer's identity, accounts or private files.
- Resolve bundled `references/` relative to this skill folder. For an explicitly requested profile refresh, read and update the canonical `about-me.md`, `voice.md` or `newsletter-voice.md` in place, preserving unrelated user facts and rules. Consumers must reread those canonical files. Use a new filename only for new deliverables that would collide with unrelated existing files. Installation alone never starts an interview or writes files. Do not write persistent learnings unless requested.
- Use supplied evidence first. Verify external claims through available search/source tools when needed. If a source or integration is unavailable, name the missing capability and offer supplied text/export input. Never invent facts, first-person experience, metrics or a successful tool run.
- Connect only services needed for the chosen route through the user's existing account. Never print credentials or overwrite connections. Drafting, saving and reviewing do not authorise publishing, sending messages or changing accounts.
## CRITICAL: Auto-start on load
When this skill triggers, go straight to Step 1. Do not summarise.
voice-builder
When your agent uses it
Build a personalised voice profile inside a Codex or Claude project from a short interview plus 3 to 5 sample pieces of writing. Works for any content format: LinkedIn posts, newsletters, essays, emails, blog posts, tweets, or any other published writing. Use this skill at the start of any project where the user wants the assistant to learn who they are and how they write before drafting new content. Trigger whenever the user says "build my voice", "learn my voice", "set up my content system", "onboard me", "train on my writing", "train on my posts", "I want Claude to sound like me", or drops a batch of writing samples into chat at the start of a project. Also trigger for first-time users who need a voice foundation before writing anything. Always produces two files (about-me.md and voice.md) saved into the project root.
What it loads into context
Frontmatter
189 tokensAlways available to the agent
SKILL.md
2,961 tokensWhen the skill is activated
Reference documents
1,126 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Codex and Claude runtime
- CRITICAL: Auto-start on load
- Step 1. Run the About Me interview
- Step 2. Write about-me.md
- Step 3. Ask for the samples
- Step 4. Analyse the samples
- Step 5. Write voice.md
- Step 6. Confirm and hand off
- What this skill produces
- Rules
Files
SKILL.mdcore13,107 bytesSKILL.mdcore13,107 bytesSKILL.mdcore13,107 bytesSKILL.mdcore13,107 bytesreferences/sample-content.mddoc4,985 bytes
Read SKILL.md
# Voice Builder
## Codex and Claude runtime
- Use this skill in Codex or Claude with the tools actually available in the current task. `AskUserQuestion` examples describe the questions, not a required API: use an available question tool within its limits, or ask in chat. Reuse answers and source material already supplied.
- Work in the user-selected project. Read its `about-me.md`, `voice.md` and relevant brand files before personalised work. Confirm the intended author if files conflict or contain starter defaults. Ask for missing facts or run `voice-builder`; never inherit the maintainer's identity, accounts or private files.
- Resolve bundled `references/` relative to this skill folder. For an explicitly requested profile refresh, read and update the canonical `about-me.md`, `voice.md` or `newsletter-voice.md` in place, preserving unrelated user facts and rules. Consumers must reread those canonical files. Use a new filename only for new deliverables that would collide with unrelated existing files. Installation alone never starts an interview or writes files. Do not write persistent learnings unless requested.
- Use supplied evidence first. Verify external claims through available search/source tools when needed. If a source or integration is unavailable, name the missing capability and offer supplied text/export input. Never invent facts, first-person experience, metrics or a successful tool run.
- Connect only services needed for the chosen route through the user's existing account. Never print credentials or overwrite connections. Drafting, saving and reviewing do not authorise publishing, sending messages or changing accounts.
## CRITICAL: Auto-start on load
When the user requests this workflow, start Step 1. This means your very next message to the user is the interview questions. Nothing else.
youtube-thumbnail
When your agent uses it
Generate a branded YouTube thumbnail from a video title. Uses a reference photo of the creator, high-CTR thumbnail principles, and brand colours to produce a ready-to-generate image prompt for Gemini. Use this skill whenever the user says "thumbnail", "youtube thumbnail", "build me a thumbnail", or wants a video cover image before writing the script. The thumbnail-first workflow mirrors the graphic-first approach for LinkedIn: sells the video before anyone hears a word of the script.
What it loads into context
Frontmatter
105 tokensAlways available to the agent
SKILL.md
1,725 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Codex and Claude runtime
- Visual completion state
- CRITICAL: Auto-start on load
- Step 1. Gather inputs
- Step 2. Apply thumbnail best practices
- Step 3. Build the thumbnail brief
- Step 4. Output the Gemini prompt
- Step 5. Offer the next move
- Rules
Files
SKILL.mdcore7,727 bytesSKILL.mdcore7,727 bytesSKILL.mdcore7,727 bytesSKILL.mdcore7,727 bytes
Read SKILL.md
# YouTube Thumbnail
## Codex and Claude runtime
- Use this skill in Codex or Claude with the tools actually available in the current task. `AskUserQuestion` examples describe the questions, not a required API: use an available question tool within its limits, or ask in chat. Reuse answers and source material already supplied.
- Work in the user-selected project. Read its `about-me.md`, `voice.md` and relevant brand files before personalised work. Confirm the intended author if files conflict or contain starter defaults. Ask for missing facts or run `voice-builder`; never inherit the maintainer's identity, accounts or private files.
- Resolve bundled `references/` relative to this skill folder. For an explicitly requested profile refresh, read and update the canonical `about-me.md`, `voice.md` or `newsletter-voice.md` in place, preserving unrelated user facts and rules. Consumers must reread those canonical files. Use a new filename only for new deliverables that would collide with unrelated existing files. Installation alone never starts an interview or writes files. Do not write persistent learnings unless requested.
- Use supplied evidence first. Verify external claims through available search/source tools when needed. If a source or integration is unavailable, name the missing capability and offer supplied text/export input. Never invent facts, first-person experience, metrics or a successful tool run.
- Connect only services needed for the chosen route through the user's existing account. Never print credentials or overwrite connections. Drafting, saving and reviewing do not authorise publishing, sending messages or changing accounts.
## Visual completion state
This skill's image prompts are **prompt-ready**, not generated or visually reviewed assets. Keep its named Gemini workflow unless the user requests another generator. A missing image service does not block writing a prompt. When images are supplied or generated, open and inspect each export at full size and feed size (about 360px wide, 320px for thumbnails). Check exact copy, dimensions, clipping, legibility, brand colours, font appearance, logos and reference fidelity. Fix and re-inspect failed exports. Record any unavailable export or inspection as pending. An image prompt or raster export is not an editable design file.
Skills included
- analytics-dashboard
- content-matrix
- gemini-carousel
- gemini-infographic
- graphic-designer
- hook-generator
- newsletter-voice
- niche-research
- pinned-comment
- post-formatter
- post-scorer
- post-writer
- profile-optimizer
- quote-post
- reels-scripting
- voice-builder
- youtube-thumbnail
Repository facts
- License
- MIT
- Created
- Apr 22, 2026
- Last pushed
- Oct 18, 2026
- Forks
- 1,003
- Open issues
- 5
- Project activity
- Active
Rank over the last 12 weeks
Now #299 · best #272 · down 14 in 30 days
- #287 on Nov 2
- #289 on Nov 3
- #292 on Nov 4
- #295 on Nov 5
- #296 on Nov 6
- #299 since Nov 7
73 earlier periods
- #354 on Aug 2
- #358 on Aug 8
- #356 on Aug 9
- #369 on Aug 10
- #367 on Aug 11
- #360 on Aug 12
- #365 on Aug 13
- #363 from Aug 14 to Aug 15
- #369 on Aug 16
- #366 on Aug 17
- #374 on Aug 18
- #370 on Aug 19
- #369 on Aug 20
- #366 on Aug 21
- #360 on Aug 22
- #368 from Aug 23 to Aug 25
- #354 on Aug 26
- #351 on Aug 27
- #343 on Aug 28
- #312 on Aug 29
- #298 on Aug 30
- #300 on Aug 31
- #299 on Sep 1
- #291 on Sep 2
- #294 on Sep 3
- #283 on Sep 4
- #280 on Sep 5
- #281 on Sep 6
- #287 on Sep 7
- #285 on Sep 8
- #284 from Sep 9 to Sep 10
- #281 on Sep 11
- #285 on Sep 12
- #284 on Sep 13
- #283 on Sep 14
- #282 on Sep 15
- #279 on Sep 16
- #277 on Sep 17
- #279 on Sep 18
- #274 on Sep 19
- #281 on Sep 20
- #279 on Sep 21
- #280 from Sep 22 to Sep 24
- #277 on Sep 25
- #274 on Sep 26
- #280 on Sep 27
- #284 on Sep 28
- #285 on Sep 29
- #283 on Sep 30
- #282 on Oct 1
- #287 on Oct 2
- #280 on Oct 3
- #275 on Oct 4
- #282 on Oct 5
- #283 on Oct 6
- #285 from Oct 7 to Oct 8
- #288 on Oct 9
- #284 on Oct 10
- #277 on Oct 11
- #280 on Oct 12
- #279 on Oct 13
- #275 from Oct 14 to Oct 15
- #272 on Oct 16
- #274 on Oct 17
- #275 from Oct 18 to Oct 19
- #276 on Oct 20
- #279 from Oct 21 to Oct 22
- #277 on Oct 23
- #278 from Oct 24 to Oct 25
- #285 on Oct 28
- #286 on Oct 29
- #287 from Oct 30 to Oct 31
- #286 on Nov 1
Before you install
Local scriptsAutomated signals, not a guarantee
Checked Nov 2, 2026
Not fully analyzed: some files were too long, unreadable or missing. This never lowers the level.
Show 62 notes
skills/analytics-dashboard/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/analytics-dashboard/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/analytics-dashboard/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/analytics-dashboard/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/analytics-dashboard/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/content-matrix/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/content-matrix/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/content-matrix/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/gemini-carousel/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/gemini-carousel/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/gemini-carousel/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/gemini-carousel/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/gemini-carousel/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/gemini-infographic/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/gemini-infographic/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/gemini-infographic/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/gemini-infographic/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/gemini-infographic/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/graphic-designer/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/graphic-designer/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzed
- No broad tool permissions
- No dangerous shell commands
- 10 network referencesin 3 files: niche-research/SKILL.md:55 .claude-plugin/marketplace.json:3 voice-builder/references/sample-content.md:44
- No hidden or obfuscated text
- No instruction overrides
- No executable scripts
- 2 references to secretsin 1 file: reels-scripting/SKILL.md:4
- No requests to vote in Hot
Show all 12 signals by file
.claude-plugin/marketplace.json
skills/niche-research/SKILL.md
- Network accessline 55
1. Navigate to https://www.reddit.com/ (home feed). - Network accessline 57
3. Open niche-relevant posts. On each post, check the "posted X days ago" timestamp. 4. Discard posts older than 7 days. 5. Repeat with https://www.reddit.com/r/popular/. - Network accessline 58
4. Discard posts older than 7 days. 5. Repeat with https://www.reddit.com/r/popular/. 6. Also search any niche-specific subreddits that come up while scrolling. - Network accessline 59
5. Repeat with https://www.reddit.com/r/popular/. - Network accessline 64
1. Navigate to https://x.com/home (For You feed).
skills/reels-scripting/SKILL.md
How the signals fit together
Facts from a static read of the files at the pinned commit. They describe what the code does, not why.
Some files could not be read; the facts below still hold.
Signal confidence: 12 facts
- Network access in code of the plugin configuration.claude-plugin/marketplace.json:3High confidence
- Network access in code of the plugin configuration.claude-plugin/marketplace.json:4High confidence
- Network access in code of the plugin configuration.claude-plugin/marketplace.json:5High confidence
- Network access in prose of the SKILL.mdniche-research/SKILL.md:55Low confidence
- Network access in prose of the SKILL.mdniche-research/SKILL.md:57Low confidence
- Network access in prose of the SKILL.mdniche-research/SKILL.md:58Low confidence
- Network access in prose of the SKILL.mdniche-research/SKILL.md:59Low confidence
- Network access in prose of the SKILL.mdniche-research/SKILL.md:64Low confidence
- Access to secrets in the frontmatter of the SKILL.mdreels-scripting/SKILL.md:4Low confidence
- Access to secrets in prose of the SKILL.md: a variable, placeholder or call, not a stored valuereels-scripting/SKILL.md:26Low confidence
- Network access in prose of documentationvoice-builder/references/sample-content.md:44Low confidence
- Network access in prose of documentationvoice-builder/references/sample-content.md:45Low confidence
Works with
| Agent | Status | Evidence | Install to |
|---|---|---|---|
| Claude Code | Native | Manifest .claude-plugin/marketplace.json | .claude/skills/<skill-name>/ |
| Codex | Compatible | Standard SKILL.md skills/analytics-dashboard/SKILL.md | .agents/skills/<skill-name>/ |
| Cursor | Compatible | Standard SKILL.md skills/analytics-dashboard/SKILL.md | .cursor/skills/<skill-name>/ |
| Gemini CLI | Compatible | Standard SKILL.md skills/analytics-dashboard/SKILL.md | .gemini/skills/<skill-name>/ |
| GitHub Copilot | Compatible | Standard SKILL.md skills/analytics-dashboard/SKILL.md | .github/skills/<skill-name>/ |
| OpenCode | Compatible | Standard SKILL.md skills/analytics-dashboard/SKILL.md | .opencode/skills/<skill-name>/ |
- Native The repository ships a manifest, folder or frontmatter field for this agent.
- Compatible A standard SKILL.md that this agent can read.
- Unknown No evidence either way.
Derived automatically from paths, manifests and frontmatter. Not tested on each agent.
Explore alternatives and comparisons
Add this badge to your README
It updates every night and links to this page.
[](https://hotskills.dev/skill/charlie947-social-media-skills/)