Content Creator
thatrebeccarae/claude-marketing
Comprehensive content marketing toolkit with brand voice analysis, SEO optimization scripts, content frameworks, social media strategy, and content calendar planning.
Map complete topic clusters for any subject area — hub pages, spoke articles, supporting content, internal linking architecture.
$ npx skills add gooseworks-ai/goose-skills --skill topical-authority-mapper -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install gooseworks-ai/goose-skills topical-authority-mapper --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/gooseworks-ai/goose-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/seo/composites/topical-authority-mapper .claude/skills/topical-authority-mapper && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "topical-authority-mapper" agent skill from https://github.com/gooseworks-ai/goose-skills/tree/main/skills/seo/composites/topical-authority-mapper into .claude/skills/topical-authority-mapper/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "topical-authority-mapper", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/gooseworks-ai/goose-skills/tree/main/skills/seo/composites/topical-authority-mapperType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add gooseworks-ai/goose-skills --skill topical-authority-mapper -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install gooseworks-ai/goose-skills topical-authority-mapper --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gooseworks-ai/goose-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/seo/composites/topical-authority-mapper .agents/skills/topical-authority-mapper && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "topical-authority-mapper" agent skill from https://github.com/gooseworks-ai/goose-skills/tree/main/skills/seo/composites/topical-authority-mapper into .agents/skills/topical-authority-mapper/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "topical-authority-mapper", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add gooseworks-ai/goose-skills --skill topical-authority-mapper -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install gooseworks-ai/goose-skills topical-authority-mapper --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gooseworks-ai/goose-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/seo/composites/topical-authority-mapper .cursor/skills/topical-authority-mapper && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "topical-authority-mapper" agent skill from https://github.com/gooseworks-ai/goose-skills/tree/main/skills/seo/composites/topical-authority-mapper into .cursor/skills/topical-authority-mapper/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "topical-authority-mapper", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/gooseworks-ai/goose-skills.git --path skills/seo/composites/topical-authority-mapper--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add gooseworks-ai/goose-skills --skill topical-authority-mapper -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install gooseworks-ai/goose-skills topical-authority-mapper --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gooseworks-ai/goose-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/seo/composites/topical-authority-mapper .gemini/skills/topical-authority-mapper && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "topical-authority-mapper" agent skill from https://github.com/gooseworks-ai/goose-skills/tree/main/skills/seo/composites/topical-authority-mapper into .gemini/skills/topical-authority-mapper/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "topical-authority-mapper", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install gooseworks-ai/goose-skills topical-authority-mapperInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add gooseworks-ai/goose-skills --skill topical-authority-mapper -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/gooseworks-ai/goose-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/seo/composites/topical-authority-mapper .github/skills/topical-authority-mapper && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "topical-authority-mapper" agent skill from https://github.com/gooseworks-ai/goose-skills/tree/main/skills/seo/composites/topical-authority-mapper into .github/skills/topical-authority-mapper/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "topical-authority-mapper", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add gooseworks-ai/goose-skills --skill topical-authority-mapper -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install gooseworks-ai/goose-skills topical-authority-mapper --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gooseworks-ai/goose-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/seo/composites/topical-authority-mapper .opencode/skills/topical-authority-mapper && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "topical-authority-mapper" agent skill from https://github.com/gooseworks-ai/goose-skills/tree/main/skills/seo/composites/topical-authority-mapper into .opencode/skills/topical-authority-mapper/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "topical-authority-mapper", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
topical-authority-mapperMap complete topic clusters for any subject area — hub pages, spoke articles, supporting content, internal linking architecture.
Topical Authority Mapper is an agent skill from gooseworks-ai/goose-skills. Map complete topic clusters for any subject area — hub pages, spoke articles, supporting content, internal linking architecture. Identifies content gaps, priority order, and builds a structured content calendar. Produces topic maps that build genuine topical authority, not random blog posts.
Its SKILL.md is about 3.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `skill.meta.json`).
It sits in Writing & Content, covering Content strategy, Blog and article writing and On-page SEO. The repository describes itself as: Library of Growth & GTM skills + data APIs for Claude Code, Codex, Cursor to run ads, social, content, lead gen, seo and data scraping. The licence is MIT.
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit c650c6d. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
python3From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
DATAFORSEO_PASSWORDKEYWORDS_EVERYWHERE_API_KEYSEMRUSH_API_KEYAHREFS_API_TOKENAPIFY_API_TOKENFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Topical Authority Mapper loads about 3.8k tokens when it runs. Until then it costs about 79 tokens; SKILL.md has 1,263 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from gooseworks-ai/goose-skills at commit c650c6d, republished under its MIT licence (© gooseworks-ai). 1,263 words, ~3,823 tokens.
.claude/skills/topical-authority-mapper/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.Most content strategies are just keyword lists turned into blog posts. Real topical authority requires a structured map: pillar pages that own broad topics, cluster pages that go deep on subtopics, and an internal linking architecture that tells Google "we comprehensively cover this subject." This skill builds that map.
Core principle: Google rewards topical depth, not random keyword coverage. A site with 15 interlinked articles that thoroughly cover "sales automation" will outrank a site with 50 unrelated blog posts that happen to mention the phrase. This skill builds the cluster architecture that creates genuine authority.
Topic cluster mapping is significantly better with keyword data that shows search volume, difficulty, and semantic relationships across hundreds of subtopic variations.
"I can build a comprehensive topical authority map using competitive analysis and content gap identification. For the most precise results — especially accurate volume data and keyword clustering at scale — I'd recommend connecting a keyword data API."
Recommended: DataForSEO (pay-per-use, ~$0.01/keyword, no monthly minimum)
- Sign up at dataforseo.com → get API login + password
- Set
DATAFORSEO_LOGINandDATAFORSEO_PASSWORDenv varsAlternatives that also work:
- Keywords Everywhere API ($1 per 10 credits = 100K keywords, very cheap) → set
KEYWORDS_EVERYWHERE_API_KEY- SEMrush API (if you have a subscription) → set
SEMRUSH_API_KEY- Ahrefs API (if you have a subscription) → set
AHREFS_API_TOKEN"Want to use one of these, or should I proceed with baseline mode? Baseline uses our existing SEO tools and web research — still produces a strong topic map, but with less granular volume data per subtopic."
seo-domain-analyzer for domain metrics, web_search for topic research, reddit-post-finder for question mining, competitor analysis via site-content-catalog. Topic mapping and cluster architecture are equally strong. Volume estimates are directional rather than exact.Run site-content-catalog on your site:
python3 skills/site-content-catalog/scripts/catalog_content.py \
--url "<your_site_url>" \
--output jsonMap all existing content:
For each competitor, run site-content-catalog:
python3 skills/site-content-catalog/scripts/catalog_content.py \
--url "<competitor_url>" \
--output jsonMap their content architecture:
Run seo-domain-analyzer for your site and competitors:
For each target topic area, generate the full subtopic universe:
Enhanced mode (DataForSEO / Keywords Everywhere):
# DataForSEO keyword suggestions
POST /v3/dataforseo_labs/google/keyword_suggestions/live
{
"keyword": "<topic>",
"limit": 500
}
# DataForSEO related keywords
POST /v3/dataforseo_labs/google/related_keywords/live
{
"keyword": "<topic>",
"limit": 500
}Extract:
Baseline mode:
Use multiple sources to build the subtopic list:
web_search for "topic + [what/how/why/best/vs/guide/examples]"reddit-post-finder for questions people ask about the topicRun reddit-post-finder for each topic area:
python3 skills/reddit-post-finder/scripts/search_reddit.py \
--subreddit "<relevant_subs>" \
--keywords "<topic>" \
--days 365 --sort top --time yearExtract:
Group all discovered keywords/subtopics into semantic clusters:
Enhanced mode: Use DataForSEO keyword clustering API or group by SERP overlap (keywords that share 3+ ranking URLs likely belong to the same cluster).
Baseline mode: Manual semantic grouping based on:
For each topic area, design the cluster hierarchy:
PILLAR: [Broad Topic] — "The Complete Guide to [Topic]"
│
├── CLUSTER 1: [Subtopic Group A]
│ ├── Article: [Specific subtopic A1]
│ ├── Article: [Specific subtopic A2]
│ └── Article: [Specific subtopic A3]
│
├── CLUSTER 2: [Subtopic Group B]
│ ├── Article: [Specific subtopic B1]
│ ├── Article: [Specific subtopic B2]
│ └── Article: [Specific subtopic B3]
│
├── CLUSTER 3: [Subtopic Group C]
│ ├── Article: [Specific subtopic C1]
│ └── Article: [Specific subtopic C2]
│
└── SUPPORTING: [Glossary terms, FAQs, tools]
├── Glossary: [Term 1]
├── Glossary: [Term 2]
└── FAQ: [Common questions]For each piece in the cluster:
| Content Type | When to Use | Typical Word Count |
|---|---|---|
| Pillar page | Broad topic overview, links to all cluster content | 3,000-5,000+ |
| Cluster article | Deep dive on subtopic | 1,500-3,000 |
| Comparison post | vs/ or alternatives content | 2,000-3,500 |
| How-to guide | Step-by-step instruction | 1,500-2,500 |
| Glossary entry | Definition + context | 500-1,000 |
| Tool/Calculator | Interactive resource | 500 + tool |
| Case study | Proof point | 1,000-2,000 |
| Listicle | Curated collection | 1,500-3,000 |
Design the linking structure:
Map specific anchor text for each link.
| Subtopic | Your Content | Competitor A | Competitor B | Volume | Difficulty | Gap? |
|---|---|---|---|---|---|---|
| [subtopic 1] | ✗ None | ✓ Pillar page | ✓ Blog post | [vol] | [diff] | ✓ High priority |
| [subtopic 2] | ✓ Thin post | ✓ Deep guide | ✗ None | [vol] | [diff] | ✓ Update needed |
| [subtopic 3] | ✓ Strong guide | ✓ Similar | ✓ Similar | [vol] | [diff] | ✗ Covered |
| [subtopic 4] | ✗ None | ✗ None | ✗ None | [vol] | [diff] | ✓ White space |
Score each content piece to create:
| Factor | Weight | Description |
|---|---|---|
| Search volume | 25% | Monthly search demand |
| Competitive gap | 25% | How much better can you be than what exists? |
| Intent alignment | 20% | Does the searcher match your ICP? |
| Cluster completeness | 15% | Does this fill a critical gap in a cluster? |
| Effort | 15% | How much work to create high-quality content? |
Based on content capacity and priority scores:
Month 1: Build [N] pillar foundations
Month 2: Deepen Cluster 1, start Cluster 2
Month 3: Complete Cluster 2, begin Cluster 3
Months 4-6: Expansion
# Topical Authority Map — [Site/Client] — [DATE]
## Executive Summary
- Topic areas mapped: [N]
- Total content pieces identified: [N] (pillars: [N], clusters: [N], supporting: [N])
- Existing content: [N] pages ([N] strong, [N] need updates, [N] gaps)
- Net new content needed: [N] pages
- Estimated timeline to full coverage: [N] months at [N] articles/month
---
## Topic Map: [Topic Area 1]
### Cluster Architecture
[Visual tree structure per Phase 3A]
### Pillar Page
- **Target keyword:** [keyword] ([volume]/mo, [difficulty])
- **Title:** [recommended title]
- **Content type:** Comprehensive guide
- **Word count target:** [X]-[Y]
- **Links to:** [all cluster articles listed]
- **Status:** [Exists — needs update / New — priority [P0/P1/P2]]
### Cluster: [Subtopic Group A]
#### Article: [Subtopic A1]
- **Target keyword:** [keyword] ([volume]/mo, [difficulty])
- **Content type:** [how-to / comparison / listicle / etc.]
- **Word count target:** [X]-[Y]
- **Links to:** Pillar + [related articles]
- **Links from:** Pillar + [related articles]
- **Priority:** [P0/P1/P2]
- **Anchor text:** "[anchor]" from pillar, "[anchor]" from [related article]
#### Article: [Subtopic A2]
...
### Cluster: [Subtopic Group B]
...
---
## Topic Map: [Topic Area 2]
...
---
## Internal Linking Matrix
| From ↓ / To → | Pillar | Article A1 | Article A2 | Article B1 | ... |
|----------------|--------|-----------|-----------|-----------|-----|
| **Pillar** | — | ✓ "[anchor]" | ✓ "[anchor]" | ✓ "[anchor]" | |
| **Article A1** | ✓ "[anchor]" | — | ✓ "[anchor]" | | |
| **Article A2** | ✓ "[anchor]" | ✓ "[anchor]" | — | | |
| **Article B1** | ✓ "[anchor]" | | | — | |
---
## Content Calendar
### Month 1: Foundation
| Week | Content Piece | Type | Cluster | Keywords | Priority |
|------|--------------|------|---------|----------|----------|
| W1 | [Pillar: Topic 1] | Pillar page | — | [kw] ([vol]) | P0 |
| W1 | [Article A1] | Cluster article | A | [kw] ([vol]) | P0 |
| W2 | [Article A2] | Cluster article | A | [kw] ([vol]) | P0 |
| W2 | [Article B1] | Cluster article | B | [kw] ([vol]) | P0 |
### Month 2: Depth
...
### Month 3: Expansion
...
---
## Coverage Gap Report
### High Priority (Competitors rank, you don't)
| Topic | Competitor Coverage | Your Status | Volume | Recommended Action |
|-------|-------------------|-------------|--------|--------------------|
| [topic] | A: Pillar, B: Blog post | None | [vol] | Create [content type] |
### Medium Priority (Weak coverage)
| Topic | Your Current Page | Issue | Volume | Recommended Action |
|-------|------------------|-------|--------|--------------------|
| [topic] | [URL] | Thin (400 words) | [vol] | Expand to [X] words, add [sections] |
### Existing Content Updates Needed
| URL | Issue | Action Required | Effort |
|-----|-------|----------------|--------|
| [url] | Outdated (2023 data) | Update stats, refresh examples | 2 hours |
| [url] | No internal links | Add [N] links to cluster articles | 30 min |
| [url] | Missing from pillar | Add link from pillar with "[anchor]" | 15 min |
---
## Metrics to Track
- **Topical coverage %** — Articles created vs. total identified
- **Internal link density** — Avg links per article within cluster
- **Cluster ranking velocity** — Time from publish to page 1 per cluster
- **Pillar page rankings** — Position for head terms
- **Organic traffic by cluster** — Traffic attributed to each topic clusterSave to the current working directory or wherever the user prefers.
For large topic maps (3+ topic areas), also export a summary CSV:
content-calendar-[YYYY-MM-DD].csv
| Component | Cost |
|---|---|
| Site catalog (your site, once) | ~$0.05-0.10 |
| Site catalog per competitor | ~$0.05-0.10 |
| SEO domain analyzer | ~$0.10-0.20 |
| Reddit scraper (per topic area) | ~$0.05-0.10 |
| DataForSEO keyword data (enhanced) | ~$0.50-3.00 (depending on keyword count) |
| Keywords Everywhere (enhanced alt) | ~$0.01-0.10 |
| Page fetches (competitor content analysis) | ~$0.01-0.05 |
| Analysis | Free (LLM reasoning) |
| Total per topic area (baseline) | ~$0.25-0.50 |
| Total per topic area (enhanced) | ~$0.75-3.50 |
| 3 topic areas (baseline) | ~$0.75-1.50 |
| 3 topic areas (enhanced) | ~$2.25-10.50 |
APIFY_API_TOKEN env varsite-content-catalog, seo-domain-analyzer, reddit-post-finder, fetch_webpageDATAFORSEO_LOGIN + DATAFORSEO_PASSWORD), Keywords Everywhere (KEYWORDS_EVERYWHERE_API_KEY), SEMrush (SEMRUSH_API_KEY), or Ahrefs (AHREFS_API_TOKEN)For ongoing topical authority tracking:
© gooseworks-ai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file in skills/seo/composites/topical-authority-mapper of gooseworks-ai/goose-skills.
Open the folder on GitHubat commit c650c6d
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in gooseworks-ai/goose-skills, which our catalogue first saw on October 7, 2026.
Topical Authority Mapper next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Topical Authority Mapper this skillgooseworks-ai/goose-skills | 1.2k | 1 repos | ~3.8k | Automated safety check: Pass | MIT | |
| Content Creatorthatrebeccarae/claude-marketing | 161 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Content Creatorsickn33/agentic-awesome-skills | 47k | 1 repos | ~2.5k | Automated safety check: Pass | MIT | |
| Blog BriefAgriciDaniel/claude-blog | 2.3k | — | ~3.2k | Automated safety check: Pass | MIT | |
| Blog BriefAgriciDaniel/claude-blog | 2.3k | — | ~3.3k | Automated safety check: Pass | MIT | |
| Writerflaqai/backlink_skills | 756 | — | ~5.8k | Automated safety check: Pass | MIT |
thatrebeccarae/claude-marketing
Comprehensive content marketing toolkit with brand voice analysis, SEO optimization scripts, content frameworks, social media strategy, and content calendar planning.
sickn33/agentic-awesome-skills
Drafts and reviews audience-specific content from supplied brand examples, with local scripts for brand voice and SEO diagnostics, channel templates and a content calendar.
AgriciDaniel/claude-blog
Generate detailed content briefs for blog posts with target keywords, content outlines, competitive analysis, recommended statistics, image and chart suggestions, word count targets, internal…
AgriciDaniel/claude-blog
Generate detailed content briefs for blog posts with target keywords, content outlines, competitive analysis, recommended statistics, image and chart suggestions, word count targets, internal…
flaqai/backlink_skills
SEO-friendly article writing, audit, and humanization workflow for Markdown content.
borghei/Claude-Skills
Full content production pipeline from blank page to publish-ready piece: research, briefs, drafting, SEO, readability, and editorial gates.
gooseworks-ai/goose-skills
Scrape and search Reddit posts using Apify. An agent skill from gooseworks-ai/goose-skills.
gooseworks-ai/goose-skills
Generate or edit an image via any FAL image model (nano-banana edit, gpt-image, flux, ...), ROUTED THROUGH THE fal-proxy so it bills the Ads agent.
gooseworks-ai/goose-skills
Replace an existing video's opening with a supplied clip or free kinetic text hook while retaining and verifying every original body frame, audio, captions and ending.
gooseworks-ai/goose-skills
Scrape blog posts via RSS feeds (free, no API key) with Apify fallback for JS-heavy sites.
gooseworks-ai/goose-skills
Find leads by scraping engagers from a competitor's top LinkedIn posts.
gooseworks-ai/goose-skills
Assemble a ChatGPT chat-reveal video ad from a thread + timeline JSON — one continuous Playwright recording of a ChatGPT mobile chat (user types with the iOS keyboard up → taps send → keyboard…
Categories
Map complete topic clusters for any subject area — hub pages, spoke articles, supporting content, internal linking architecture. Topical Authority Mapper is an agent skill from gooseworks-ai/goose-skills. Map complete topic clusters for any subject area — hub pages, spoke articles, supporting content, internal linking architecture.
Topical Authority Mapper fits situations like: tasks that involve Content strategy; tasks that involve Blog and article writing; tasks that involve On-page SEO.
Run `npx skills add gooseworks-ai/goose-skills --skill topical-authority-mapper -a claude-code`. Or copy the skill folder (skills/seo/composites/topical-authority-mapper in gooseworks-ai/goose-skills) into .claude/skills/topical-authority-mapper in your project. Claude Code loads it when a task matches its description.
Run `npx skills add gooseworks-ai/goose-skills --skill topical-authority-mapper -a codex`. Or copy the skill folder (skills/seo/composites/topical-authority-mapper in gooseworks-ai/goose-skills) into .agents/skills/topical-authority-mapper in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add gooseworks-ai/goose-skills --skill topical-authority-mapper -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/topical-authority-mapper, .gemini/skills/topical-authority-mapper, .github/skills/topical-authority-mapper and .opencode/skills/topical-authority-mapper in your project.
Going by SKILL.md and its folder, Topical Authority Mapper needs the command-line tools its instructions call (python3) and credentials named DATAFORSEO_PASSWORD, KEYWORDS_EVERYWHERE_API_KEY, SEMRUSH_API_KEY and AHREFS_API_TOKEN. Our summary lists: Python 3; A credential in KEYWORDS_EVERYWHERE_API_KEY; A credential in SEMRUSH_API_KEY.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Topical Authority Mapper is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.8k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Topical Authority Mapper: Content Creator (thatrebeccarae/claude-marketing, 161 stars), Content Creator (sickn33/agentic-awesome-skills, 47k stars), Blog Brief (AgriciDaniel/claude-blog, 2.3k stars) and Blog Brief (AgriciDaniel/claude-blog, 2.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
gooseworks-ai (a GitHub organization) maintains it in gooseworks-ai/goose-skills, which has 1,240 GitHub stars. The repository holds 273 skills in this directory. The repository was last updated on October 8, 2026.
Source: gooseworks-ai/goose-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.