Replace broken agent-skill.co directory links with smithery.ai in README#179
Open
tomash wants to merge 3 commits intoheilcheng:mainfrom
Open
Replace broken agent-skill.co directory links with smithery.ai in README#179tomash wants to merge 3 commits intoheilcheng:mainfrom
tomash wants to merge 3 commits intoheilcheng:mainfrom
Conversation
Official Skill Directory links used agent-skill.co/OWNER/skills/NAME paths that now return 404. Point them at smithery.ai/skills/OWNER/NAME instead. Header links to the live directory homepage are unchanged.
|
@tomash is attempting to deploy a commit to the heilcheng's projects Team on Vercel. A member of the Team first needs to authorize it. |
Author
|
Hi, actual human owner of the account here. The code and PR is entirely agent-generated, but came from my instructions. Not sure if Smithery is the "official" successor to agent-skill directory. I've checked the links and most of them work. There are a few owners (Minimax-AI, Netlify, vercel-labs and some others) that I can't find on Smithery nor in any other skill registry online, so those links stay dead. |
- Vercel: link to vercel-labs/agent-skills and vercel-labs/next-skills on GitHub - MiniMax: link to MiniMax-AI/skills tree paths (not on Smithery) - Netlify: note missing Smithery listings; use npx skills find and GitHub code search Smithery often returns 200 with a generic page title when a skill is absent.
Audit: many smithery.ai/skills URLs return 200 with the generic site title instead of a real skill page. Replace those with verified GitHub tree links, plugin paths, or GitHub code searches; add a short note under Official Skill Directories. Covers Gemini, HF (hf-cli, transformers-js), DuckDB, GSAP, VoltAgent, replicate/remotion/fal, Trail of Bits plugins, Sentry code-review path, Firecrawl CLI, Microsoft cloud-solution-architect, garrytan/gstack, Better Auth, Binance/Figma/Tinybird/Workspace/Notion where no stable repo path, and fixes Sanity agent-toolkit table paths (skills/ prefix).
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
1 participant
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.
Summary
The Official Skill Directories section in
README.mdlinked skills with URLs of the formhttps://agent-skill.co/OWNER/skills/SKILLNAME. Those paths now return 404, so readers hit dead ends when following curated official skills.This change rewrites those links to Smithery using the mapping:
https://agent-skill.co/OWNER/skills/SKILLNAME→https://smithery.ai/skills/OWNER/SKILLNAME152 skill links are updated. The banner / quick-start references that only point at the
agent-skill.cohomepage (without/OWNER/skills/...) are left as-is.Verification
Sample
curlchecks (one URL per distinct owner) against smithery returned HTTP 200, not 404.Process note
The edits were produced agentically (automated assistant), then reviewed and verified by a human (Tomash) before this PR—including spot-checking that the new URL pattern resolves.
Happy to adjust wording or extend the same treatment to localized READMEs if maintainers want consistency across locales.