Samuel BertheCreator of Go library lo, 21k+ GitHub stars377 installs on skills.shAPI Reference Quality
Audit a published API reference at the endpoint level against its spec surface - every operation.
3 static scans, 0 counted findings.
Edge checks it again each time your agent loads it.
From the samber public repository. Edge did not write or edit this skill.
What it does
- Audit a published API reference at the endpoint level against its spec surface - every operation, parameter, response code, and error documented, request/response examples present, per-language code snippets in parity, try-it affordances working - and install the source-of-truth gates that stop reference drift (spec-driven generation, OpenAPI lint, contract tests, snippet parity in CI).
- Use whenever the user mentions API reference docs, OpenAPI docs completeness, undocumented endpoints or error codes, stale or drifting docs, or docs CI gates - even if they never say "reference quality".
- Endpoint-level reference only.
- Do NOT use for portal IA and onboarding - use samber/developer-platform-skills@developer-portal-design instead.
Why Samuel Berthe
Go open source author. Each fact links its public source.
- Created samber/lo, 21k+ stars
His Lodash-style Go generics library lo has 21k+ GitHub stars.
GitHub - Packaged in Ubuntu
lo ships as an Ubuntu source package, golang-github-samber-lo.
Ubuntu packages - 3k+ stars on his Go skills
His Golang agent skills collection has 3k+ GitHub stars.
GitHub
Public sources, checked Oct 26, 2026.
How it works
- 1Copy
Try for free gives you one prompt.
- 2Paste
Paste it into Claude Code, Codex or Cursor.
- 3Ask
Ask for the outcome. Your agent loads API Reference Quality.
3 static scans, 0 counted findings.
Security state at 2026-09-30: reviewed. Static scans check the code, not how well the skill works.
State definitionsSkill details
Security scansReviewed
3 static scans, 0 counted findings. Security state at 2026-09-30: reviewed. Edge checks it again each time your agent loads it.
Edge static checks (Edge-run): edge-static/1.0.1. Scope: Static patterns for remote execution, credentials with network sends, obfuscation, prompt overrides, hidden Unicode, binaries and persistence. Raw findings: .
Cisco skill-scanner (Edge-run): cisco-skill-scanner/2.1.0. Scope: Local static, YARA, pipeline and behavioral analyzers; no LLM or AI Defense analysis. Raw findings: .
Semgrep Edge rules (Edge-run): semgrep/1.178.0+edge-rules.c15016a36fd3+offline-v1. Scope: Six Edge-authored static rules with Semgrep CE; offline execution and metrics disabled. Semgrep-maintained rules excluded. Raw findings: .
- Edge static checks
- Pass · 0 counted findings · 2026-09-27
- Cisco skill-scanner
- Pass · 0 counted findings · 2026-09-27
- Semgrep Edge rules
- Pass · 0 counted findings · 2026-09-27
Creator, source & licencesamber
From the samber public repository. Edge did not write or edit this skill.
- Repository
- samber/developer-platform-skills
- Skill file
- View source at revision
- Revision
- 37219ca68b5b97789172a67d6241e7524577f949
- Package hash
- sha256:9e48703c1fdb6720452214d3a73f467dc8a5f1f4cc57288f9da8e15b537a6b73
- Licence
- MIT
- Description
- Audit a published API reference at the endpoint level against its spec surface - every operation, parameter, response code, and error documented, request/response examples present, per-language code snippets in parity, try-it affordances working - and install the source-of-truth gates that stop reference drift (spec-driven generation, OpenAPI lint, contract tests, snippet parity in CI). Use whenever the user mentions API reference docs, OpenAPI docs completeness, undocumented endpoints or error codes, stale or drifting docs, or docs CI gates - even if they never say "reference quality". Endpoint-level reference only. Do NOT use for portal IA and onboarding - use samber/developer-platform-skills@developer-portal-design instead.
Quoted from the skill’s own description
Questions about API Reference Quality
What does API Reference Quality do?
Audit a published API reference at the endpoint level against its spec surface - every operation. Published by Samuel Berthe (samber/developer-platform-skills).
Is API Reference Quality safe to use?
Edge security state: Reviewed (3 Edge-run static scans, scanned Sep 30, 2026). The Evidence tab shows the scan.
How do I use API Reference Quality in Claude Code, Codex or Cursor?
Click Try for free, pick your agent and follow its one step. Edge is free, with no Edge account.