Skip to content

refactor: restructure skill markdown URLs and improve the site#171

Merged
raymondk merged 9 commits intomainfrom
rk/refactor
Apr 16, 2026
Merged

refactor: restructure skill markdown URLs and improve the site#171
raymondk merged 9 commits intomainfrom
rk/refactor

Conversation

@raymondk
Copy link
Copy Markdown
Collaborator

@raymondk raymondk commented Apr 16, 2026

  • return markdown urls from .well-known
  • add note about not relying on cache
  • fix the text on how it works
  • add the source commit for a skill
  • add times and commit to skill

@raymondk raymondk requested review from a team and JoshDFN as code owners April 16, 2026 18:17
@raymondk raymondk enabled auto-merge (squash) April 16, 2026 18:26
@marc0olo
Copy link
Copy Markdown
Member

Looking good. Two remaining things:

  • api/skills.json.ts and api/skills/[slug].json.ts still use githubUrl() (main branch) for urls.source. Now that the skill page shows a commit-pinned link, the JSON API is out of sync — updated date and source URL describe different versions. Worth switching to githubCommitUrl (needs getSkillGitInfo in those two files).

  • Nit: the new .ic-assets.json5 entry is commented "User discovery endpoints" — the adjacent rule says "Agent discovery endpoints". Suggest something like "Raw skill markdown endpoints" to match what it actually is.

@github-actions
Copy link
Copy Markdown

Skill Validation Report

No skill files were changed in this PR — validation skipped.

@marc0olo
Copy link
Copy Markdown
Member

Thanks — api/skills/[slug].json.ts looks good now. api/skills.json.ts (the full index) still uses githubUrl() for urls.source. Since getSkillUpdatedAt already calls getSkillGitInfo internally, the SHA is already being computed and discarded — a small refactor to destructure it would make the index consistent too. Low priority, but worth tracking.

@raymondk raymondk merged commit 43ece34 into main Apr 16, 2026
6 checks passed
@raymondk raymondk deleted the rk/refactor branch April 16, 2026 19:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants