Your expertise. Their superpower.
A public GitHub link in, a finished public Skill page out — pinned to the exact commit, with the licence the repository declares and a SHA-256 of every file.
getedge reads the source you point it at, builds the page from what your SKILL.md says and nothing else, and records the repository, the exact commit, the licence the repository declares and a hash of every file. Where the file declares no outcome, no inputs and no prerequisites, those stay empty on the published page rather than being written for you. Nothing here is reviewed and nothing is endorsed: getedge asserts no Trust state over a published Skill, publishes no install counts, and credits the account the repository is owned by rather than claiming to know who wrote it.
Who may publish today
Nobody, yet. Writing into the public catalog is open only to accounts getedge has let in, and that list is empty on this deployment. This page is here so the mechanism is legible before the door opens, not so a submission can be queued against it — there is no queue, no reviewer and no pending state to be in.
Publishing writes to the public getedge catalog, so it needs an account. Sign in first.
Signing in does not by itself open publishing. Write to [email protected] if you want an account let in.