Repository navigation
perf(registry): shorten the local Skill fork workflow - #421
Conversation
🤖 MERGED
GitHub merged this pull request.
86d4d52d-5a48-498d-b9c7-a5d000dd6db7 Selected findings run after merge and open separate pull requests. |
|
Production workflow and timing checked by Codex, because CI cannot perform fresh-Agent trials:
Both fresh Agents received a normal URL and an isolated Codex project. They received no implementation history. The preview used production HTML fetched before timing and candidate Markdown from the exported composer. Metadata and Git remained live, at the same source commits as the earlier trials. These are single-model smoke trials, not a general speed benchmark. Neither Agent tried install JSON output or fetched full Git history. Independent checks verified original source bytes and modes, licence evidence, provenance, local lock records, and Agent copies. Edited copies survived reinstall. Upstream checks identified local sources. The built Cloudflare application also served the fork-only query response from The generated candidate guide measured 2,928 bytes for generate-package-skill and 2,863 bytes for find-skills. Earlier live Markdown measured 12,071 and 8,115 bytes. The fixture responses excluded module-added frontmatter and sitemap text. |
There was a problem hiding this comment.
Harlan Agent Kit posted this automated review. AI open source policy.
Automated Review: READY.
|
Codex Agent verified production after merge. Deploy run 37316365035 passed at descendant 389db91. Both normal Skill pages link to the fork-only guide. Both guides return HTTP 200 and include shallow fetch and plain install. Normal Markdown still includes the full Skill. Evidence: https://notes.localhost/notes/skilld-fork-speed |
🔗 Linked issue
Follow-up to #418.
❓ Type of change
📚 Description
Agents spent 103–178 seconds forking Skills while reading extra instructions and retrying unsupported install JSON output. Fork links now request a short fork-only guide, with a shallow fetch at one commit, batched checks, and plain installation output.
Two fresh preview trials took 96s and 115s, compared with 103s and 178s in earlier live trials. These are single-model smoke trials using preloaded HTML fixtures.