rohitabrahamgeorge
UserVoice-driven time tracking, project management and daily priorities in Notion, run by Claude. Say it and Claude moves the task.
Categories
Indexed Skills (21)
northstar
Voice-driven time tracking, project management and daily priorities in Notion, run by Claude. Say what you did and it moves the tasks. Tells you which task is most important, which to do first and which is most urgent, runs one timer at a time, turns Notion AI meeting notes into your tasks, and writes a weekly time report. Use for anything involving tasks, timers, time logs, priorities, meeting actionables or weekly hours in Notion. Trigger on "what should I do next", "what's most urgent", "what's my priority today", "plan my day", "start a timer on", "stop the timer", "I'm starting work on", "I'm done", "switch to", "log 2 hours on", "what are my tasks", "what's on my plate", "create a task", "add a task", "close this task", "mark it done", "process my meetings", "pull actionables from my meeting notes", "weekly report", "how did my week go", "hours this week", "set up Northstar", spoken commands like "that's done", "I'm on X now", "push X to Friday", "bump it to P0", or any mention of Northstar or Northstar
blog-seo-auditor
B2B SEO auditor and content optimization specialist for {{BRAND}} blog posts written for founders, marketers, business leaders, experts and operators. Runs a five-phase audit covering headline and H1, keyword usage and placement, search intent alignment, structure and executive skimmability, internal and external linking, engagement and SERP optimization, then outputs a scorecard with prioritized, specific edits. Use whenever the user asks to audit a blog post, review a draft for SEO, improve search performance on an article, check keyword placement, optimize H2s for CTR, find internal link opportunities, or grade a post before publishing. Trigger on phrases like "audit this blog", "SEO review this post", "how do I rank this", "check the keywords in this article", "optimize this for search", "score this draft", or any handoff of a finished blog article for review. Also runs automatically as the final QA stage of the {{BRAND}} episode repurposing engine. Does not rewrite the whole article unless asked.
broll-researcher
Analyzes {{SHOW_NAME}} podcast transcripts and recommends specific, sourceable B-roll footage for each segment, grounded in deep research about the guest, their company, and the topic. Use this skill whenever the user provides a podcast transcript and asks for B-roll suggestions, b-roll research, footage recommendations, visual research, or video edit assets for a {{SHOW_NAME}} episode. Trigger aggressively on phrases like "find b-roll for this episode", "research b-roll", "what footage should we use", "build the b-roll list", "b-roll suggestions", "visual assets for the cut", "footage for the editor", "research visuals for this podcast", "broll for the [guest name] episode", or any time a podcast transcript is shared alongside a LinkedIn profile URL or guest name and visual research is needed. Outputs a structured per-segment list with verbatim transcript excerpts, the exact 7-second window, a described visual asset, a verified source URL, fit reasoning, and a confidence rating the editor can triage on.
carousel-deck-architect
Turns any topic, idea, transcript, rough note, or content brief into a complete publish-ready Instagram or LinkedIn carousel in ONE shot, with per-slide copy plus a per-slide Gemini image generation prompt and the overlay design spec. Use this skill aggressively whenever someone wants a carousel, a slide deck for social, an Instagram carousel, a LinkedIn carousel, a swipe post, a content carousel, or asks to "turn this into slides", "make a carousel about X", "build a carousel from this podcast", "I need image prompts for each slide", "give me slide copy and visuals", "design a carousel deck", "write a swipe post", "carousel from this transcript", "turn this idea into a carousel", or shares a topic and asks what the slides should say and look like. Also trigger when someone wants image generation prompts for a multi-slide social asset, or asks how a carousel should be structured, sequenced, or designed. Produces copy, Gemini prompts, and overlay specs in a single pass without asking clarifying questions.
clip-curator
Turns a "{{SHOW_NAME}}" transcript into FOUR fully built Instagram reels using the Triple Hook Framework of Context, Lean and Snapback. Each reel ships with the exact chosen transcript and timestamps, a non-sequential assembly map, a timed on-screen text schedule including the comment CTAs, and a full editor build sheet. Names exactly one reel as the trial pick and staggers the rest. Use whenever the user shares a transcript and wants clip ideas, reel picks, viral moments, shorts candidates, the trial pick, hooks, on-screen text, or an editor brief. Trigger on "find the best clips", "what should we cut for reels", "pull viral moments from this episode", "clip this transcript", "build the reels", "which one goes to trial", "build the reel brief", or "editor brief for this clip". Enforces the rules learned from live Instagram trials, meaning one trial reel at a time and never a recut of a cut that already ran. Trigger aggressively for any short-form clip or reel request.
lead-magnet-playbook
Lead Magnet Architect for {{BRAND}}. Turns a "{{SHOW_NAME}}" session transcript into an execution-ready lead magnet playbook optimized for LinkedIn virality and content-led GTM growth, built only from what the transcript actually contains. Runs a strict process, meaning extract the topics, find the unifying growth narrative, propose three angles, then STOP for the user to choose before writing anything. Use whenever the user wants a lead magnet, freebie, gated asset, downloadable playbook, checklist or growth guide built from a podcast transcript or session recording. Trigger on phrases like "build a lead magnet from this", "turn this episode into a playbook", "what gated asset comes out of this transcript", "lead magnet angles for [guest]", "make a downloadable from this session", or any transcript shared with intent to produce a gated asset. Trigger aggressively for anything lead-magnet related sourced from a transcript.
podcast-blog-writer
Turns a "{{SHOW_NAME}}" podcast transcript into a publish-ready, SEO-optimized long-form blog article for founders, marketers, GTM leaders and operators. Runs in two phases, meaning first it proposes 2 to 3 editorial theses each with a low-difficulty keyword map and STOPS for the user to choose, then it writes the full article with title, scannable body, URL slug and five meta description options. Use whenever the user wants a blog post, article, written recap or SEO piece built from a podcast transcript or episode. Trigger on phrases like "write the blog from this episode", "turn this transcript into an article", "blog post for the [guest] episode", "what should the blog angle be", "SEO article from this podcast", or any transcript shared with intent to produce long-form written content. Trigger aggressively for any transcript-to-blog request for {{BRAND}}.
podcast-repurposing-engine
Master orchestrator that turns a single "{{SHOW_NAME}}" transcript into the full repurposing set in one coordinated run. Use this whenever the user shares a new podcast transcript, episode notes, or a recording link and wants the whole package rather than one asset. Trigger aggressively on a bare transcript drop, or on phrases like "run the full pipeline on this episode", "repurpose this transcript", "do everything for this episode", "give me the works for [guest]", "fire all the skills on this", or "process this episode". This engine coordinates five sub-skills in order, meaning clip-curator, youtube-packaging, podcast-blog-writer, lead-magnet-playbook, and blog-seo-auditor. When a full repurposing run is requested, this orchestrator OWNS the sequence. Do not fire those five skills independently for a whole-episode run. If the user names only specific deliverables, run just those. Also sequences trailer-architect, broll-researcher and carousel-deck-architect as on-request add-ons.
trailer-architect
Builds 90-to-120-second cold-open trailer scripts from full podcast transcripts of "{{SHOW_NAME}}." Use this skill whenever the user provides a podcast transcript and asks for a trailer, teaser, promo, cold open, viral cut, highlight reel, or social cutdown for the {{BRAND}} podcast. Trigger aggressively on phrases like "make a trailer for this episode," "build a teaser," "stitch the best moments," "create a promo," "cold open for the podcast," "viral clip stitch," "trailer for the [guest name] episode," or any request to produce a short-form promotional cut from a {{BRAND}} podcast transcript. The output is a YouTube and Spotify ready trailer script with verbatim quotes, host integration, and a structured trailer arc tuned to the show's B2B GTM and AI audience.
youtube-packaging
Builds the full YouTube publishing package for a "{{SHOW_NAME}}" episode from its transcript, meaning hero moment extraction, three title and thumbnail combo sets, the video description, timestamped chapters, tags, hashtags and a testing note. Use whenever the user needs YouTube titles, thumbnail concepts, a video description, chapters or tags for a podcast episode. Trigger on phrases like "YouTube package for this episode", "write the YouTube title and description", "thumbnail ideas for [guest]", "chapters for this episode", "what should we call this on YouTube", or any transcript shared with intent to publish the full episode to YouTube. Trigger aggressively for any YouTube packaging request for the {{BRAND}} podcast.
blog-manager-sop
Static SOP document for the human blog manager running a hub-and-spoke publishing cycle for the product described in product-context.md. This is not an agentic skill. It is a reference document the blog manager reads to understand how the cluster system works, what publishes when, in what order, and how to handle exceptions. Trigger on phrases like "what's the publishing cycle", "how does the hub-and-spoke model work", "when should I publish post 4", "what's the SOP for clusters", "blog manager handbook", or any question about the operational publishing rhythm. The blog manager (whoever owns publishing on the team) consults this doc before every publish action.
cluster-link-validator
Validates the internal link topology of a content cluster before publish. Confirms every spoke links back to the pillar, the pillar links to every spoke, anchor text is descriptive and keyword-rich, and no external competitor links have leaked through. Use this skill after the writer has produced posts and the quality-checker has passed them, but before publish. Trigger on phrases like "validate links", "check the link topology", "audit cluster links", "is the cluster bidirectional", "are there any broken internal links", or any handoff that asks for the link-level gate before publishing. This skill produces a pass/fail report and does not edit content. The blog manager or writer fixes any issues before publish.
cluster-orchestrator
Master orchestrator for building complete SEO content clusters for competitor comparisons of the product described in product-context.md. Use this skill whenever the user asks to build a content cluster, run the cluster system, create a "[Product] vs [Competitor]" content set, build a comparison cluster, run the hub-and-spoke playbook, or starts a request with "{{PRODUCT}} vs", "[Product] vs [Competitor]", "build cluster for", "compete with", or "[Competitor] alternatives cluster". This skill reads the cluster name from the user, confirms scope, and then orchestrates the full chain of cluster skills (planner, writer, quality-checker, visual-designer, link-validator, performance-tracker, performance-optimizer) by telling Claude which skill to invoke at each stage. The blog-manager-sop is a static reference doc, not invoked. Trigger this skill aggressively for ANYTHING related to building a competitor comparison content cluster. This is the master skill, so do NOT invoke individual cluster skills directly when
cluster-performance-optimizer
Analyzes published cluster posts against fresh GSC performance data and outputs specific, actionable change recommendations to improve rankings and AEO citations. Use this skill after the performance-tracker has produced a 15-day report, when the blog manager asks "what should we change to improve [post/cluster]", when a post has been flagged as significantly degraded, or when a cluster has had 3+ stable cycles and the team wants to push gains further. Trigger on phrases like "optimize this post", "what changes will improve ranking", "AEO recommendations", "GSC-based optimization", "improve cluster performance", or any request to translate GSC data into editorial action. This skill produces recommendations only. It does not edit content. The blog manager implements minor changes; the cluster-writer handles major rewrites.
cluster-performance-tracker
Tracks the performance of published cluster posts on a 15-day cadence. Reads live blog URLs to confirm published metadata (title, slug, primary keyword, publish date), ingests GSC data from a manually-exported CSV, updates the cluster Google Sheet (the single source of truth), and generates a 15-day monthly report. Use this skill on the recurring 15-day cadence after a cluster is published, whenever the blog manager runs "the performance check," when GSC data has been freshly downloaded and dropped into the input folder, or when someone asks "how is the [cluster] cluster performing." Trigger on phrases like "run the 15-day check", "update the cluster Google Sheet", "pull GSC data", "performance report for [cluster]", "monthly cluster report", or any handoff from the blog manager that asks for the cadence-based performance update. This skill does not edit content. It tracks what's already published.
cluster-planner
SERP analyst and content planner for competitor comparison clusters ({{PRODUCT}} vs {Competitor}). Use this skill when the orchestrator delegates planning, OR when the user asks to "plan a cluster", "research SERPs for", "do keyword research for", "analyze competitors for", "build a content plan for", or wants a content brief for a competitor comparison topic. This skill performs deep SERP analysis on parallel competitor pairs (since head-to-head {{PRODUCT}} vs X queries usually have no organic data), pulls People Also Ask, identifies content gaps, references the product's help center or knowledge base, and outputs a complete cluster plan as both markdown and a Google Sheets-compatible TSV tracker. It reads product-context.md for every product fact and runs a short intake to create it if missing. Trigger this skill aggressively for ANYTHING involving SERP research, content planning, keyword analysis, or hub-and-spoke architecture for competitor comparison clusters. The output is the input to cluster-writer, s
cluster-quality-checker
Audits cluster posts against the 13 strict PostHog template rules and outputs a pass/fail report with specific corrections. Use this skill after the writer hands off a draft and before the post goes to publish. Trigger on phrases like "QA this post", "quality check the pillar", "audit the listicle", "did the writer follow the rules", "run the checklist on these posts", or any handoff from the writer or orchestrator that asks for verification before publish. This skill does not rewrite content. It produces a structured report that the writer or human editor uses to fix issues. Trigger aggressively on any cluster post entering the QA stage.
cluster-visual-designer
Designs the small, specific set of visuals that a PostHog-style cluster post actually needs. Use this skill when the orchestrator hands off a written post (or set of posts) for visual treatment. Triggers on phrases like "design the visuals for the pillar", "generate the hero image", "create the CTA banner for this post", "visualize the cluster post", or any handoff from cluster-writer with a complete post. This skill follows PostHog's verified visual pattern (1 hero image per post, 1 product screenshot per main listicle entry, 2 repeated CTA promo banners, 1 newsletter banner). It does NOT produce infographics, decision trees, comparison flowcharts, or feature-section diagrams because PostHog does not. The output is SVG specs and image briefs that can be handed to a designer or rendered programmatically.
cluster-writer
Writes publish-ready posts for a {{PRODUCT}} SEO content cluster following the strict PostHog hub-and-spoke template. Use this skill whenever the orchestrator hands off a post type (pillar, alternatives listicle, migration guide, narrative, pricing explainer, 3-way comparison, B2B review, or category explainer) for a {{PRODUCT}}-vs-competitor cluster. Trigger on phrases like "write the pillar", "write the listicle", "write the migration guide", "write post 4 of the cluster", "draft the comparison post", or any handoff from cluster-orchestrator with a confirmed plan and SERP analysis. This skill codifies the strict line-by-line PostHog rules verified by direct fetches of posthog.com/blog/posthog-vs-mixpanel and posthog.com/blog/best-mixpanel-alternatives. Do not invent features, do not add quick-answer blocks, do not use years in headlines, do not link to external competitor sites. Every product claim must be documented in product-context.md.
seo-blog-writer
Produces top 1% on-page SEO blog posts for SaaS and B2B brands using the hub-and-spoke topic cluster model. Use this skill whenever the user asks to write a blog post, comparison post, alternatives post, listicle, product review, or any long-form content that needs to rank on Google. Also trigger on: 'write a blog', 'SEO blog', 'comparison post', 'alternatives post', 'vs post', 'best X tools', 'X vs Y', 'competitor comparison', 'topic cluster', 'pillar page', 'hub and spoke content', 'rank for keyword', 'on-page SEO', 'write content that ranks', 'blog post outline', 'SEO outline', 'content brief', or any request to produce a blog post optimized for organic search. Trigger aggressively -- if there is any mention of blog writing, SEO content, comparison content, or ranking for keywords, use this skill.
seo-coach
Friendly SEO coach mode for the SEO Content Team skill pack, powered by the Semrush MCP. Explains what each workflow does, reads the user's real Semrush data, and recommends the single best next step. Use whenever the user asks "where do I start with SEO", "what should I do next", "coach me", "explain this SEO report", "which skill should I use", "how do I use Semrush with Claude", "is my site ready for a content cluster", or seems unsure which workflow fits. Also use when the user is new to SEO and needs concepts explained in plain language before running anything.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.