meta: carry the category phrase and tags in the strings marketplaces display - #6
Merged
Merged
Conversation
…display Directory listings that outrank webmcpify.at for its own brand name describe the skill wrongly — one files it as an "MCP Server", another as an "Antigravity agent skill". They read SKILL.md frontmatter and the manifest descriptions, and neither carried the phrase "WebMCP agent skill" nor any tags to categorize by. Adds tags to SKILL.md, puts the phrase at the front of the SKILL.md, package.json and skill.json descriptions and in the README h1, and records both constraints in AGENTS.md so the next edit does not quietly drop them. npm run check: 17/17.
…lity # Conflicts: # skill.json
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Measured 2026-08-05: a Google search for
webmcp agent skillsurfaces no webmcpify resultat all, and on the brand query
webmcpifythe top ten are third-party directories —webmcpify.atitself does not appear. Those directories therefore are the descriptionmost humans and AI answers get, and they get it wrong:
mcpservers.orgfiles this skill as"Webmcpify (agent Skill) MCP Server",
awesomeskills.devcalls it an "Antigravityagent skill", and three others credit
github/awesome-copilotrather than TueJon.They read
SKILL.mdfrontmatter and the manifest descriptions. Neither carried the phrase"WebMCP agent skill", and
SKILL.mdhad notags:at all — so a crawler that wants acategory has to invent one.
Diagnosis:
devlog/history/generic/2026-08-05-webmcpify-search-visibility-diagnosis.md·lesson:
knowledge/generic/webmcpify-search-visibility-root-cause.md(workbench).What changed
SKILL.md:tags:(webmcp, agent-skill, document.modelContext, browser-agents,web-development, chrome) and the category phrase at the front of the
description—trigger phrases (
"webmcpify","add WebMCP","expose app actions to AI agents")are unchanged.
package.json+skill.jsondescriptions, and the README<h1>: same phrase.AGENTS.md: records both constraints — why the phrase must stay, and that thefrontmatter is plain YAML, so no
:in an unquoted scalar (the first draft of thischange used "WebMCP agent skill: make a web app…" and would have broken every
consumer's parser; caught by parsing the frontmatter, not by eye).
Verification
npm run check→ typecheck + syntaxcheck + 17/17 tests. Frontmatter parsed withPyYAML: all five keys resolve,
tagsis a list. Versions untouched, so manifest parityholds.
Not in this PR (needs Jonas)
The
v0.3.0release tag (several directories gate on stars/releases; this repo has 2 starsand no tag), corrections/recrawls at the directories themselves, and the
webmcpify.at/webmcp-agent-skill/page that pairs with this — TueJon/webmcpify.at#8.