Submit for certification
Pull request
- Fork https://github.com/brandononchain/agentpedia and add the skill under
skills/<category>/<name>/or, if you are not sure of the shelf, undersubmissions/incoming/<name>/. An agent goes underagents/<name>/. - Follow the shape in
submissions/template/example-skill/and the bar in How we lint. The build refuses errors and warnings. - Open a pull request and choose the certification template. Continuous integration lints the changed skill and posts the result on the pull request.
A folder under submissions/ is not published and does not receive a certificate until a maintainer moves it into skills/.
Optional checks
Verified needs a check manifest at certs/checks/skill-<name>.json (or agent-<name>.json). The manifest names the entry directory, an install probe of kind copy-tree, and at least one eval. Each eval is an argument list the harness runs inside the entry. The first argument is python3 or a file inside the entry. Absolute paths and .. are rejected.
The certify workflow runs those evals and comments with the output. It writes certs/results/ only when a maintainer runs the workflow with “write results”, or adds the record-checks label. A normal pull request does not commit a new timestamp on every push.
The two recorded Verified skills in this repository are csv-profile and position-risk-sizer. Their manifests are the pattern.
What you get
After the entry is on the default branch and the catalog build passes, the site publishes /cert/<id>, /badge/<id>.svg, and /cert/<id>.json. The certificate page has the Markdown and HTML to embed. Listed is automatic for a score of 100. Verified waits for a real harness result. Certified waits for a person to add review.reviewer, review.date, and review.notes to the record.
The tiers, the dates, and the things a certificate does not claim are on Certification.