agentleFS
kostja94kostja94/marketing-skills/skills/keyword-mapping/SKILL.md

keyword-mapping

Skill1.1k starsChanged 25 days agoMITView on GitHub

Maps keyword clusters to existing website assets and recommends reuse, improvement, consolidation review or a new page.

1 other project uses a version of this.

Trending

More talk lately.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 1 mentionApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 2 mentionsNov 2026: 1 mention
Dec 2025Jun 2026Nov 2026
Mentions a month of the kostja94/marketing-skills repository that our weekly crawl found: only 4 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Start with the clusters, site inventory and product capabilities.

    line 10
  2. Distinctive:

    When an existing site's inventory is missing or uncertain, use site-structure-inventory to verify live pages, URL families and discovery …

    line 19

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Keyword Mapping

Start with the clusters, site inventory and product capabilities. Obtain candidate URLs from a sitemap, navigation, crawl or user inventory. Open the page to verify the action it supports, promised result and conversion path. If inventory is incomplete, mark coverage unknown.

Reuse a page that serves the task. Improve it for a supported task with missing content or discoverability. When multiple pages serve the same task, review overlap before suggesting consolidation. Recommend a new page only for a distinct supported task with no adequate asset. A separate cluster can still fit a distinct mode on an existing tool. Defer unsupported or uncertain tasks.

Return cluster, current URL (or proposed asset type), action, rationale and required verification. Send implementation to the relevant page or content skill. Keep redirects, publishing and content production as separate decisions.

When assets are unavailable, return a provisional map with illustrative relative URLs and stated product assumptions. Group same-page variants under one URL. Explain when a modifier warrants an on-page option versus a dedicated landing page. Assign a blog guide when the user wants instruction and evidence supports that reading. Avoid generating an entire modifier-by-page matrix from an untested pattern.

When an existing site's inventory is missing or uncertain, use site-structure-inventory to verify live pages, URL families and discovery gaps before making recommendations.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.