DeveloperA
C4 Architecture Diagram
Turn a system description into a simple diagram and clear notes about what is unknown.
- Security score Why?
- 100/100
- Last used
- 2026-10-26
- Success ratio
- No reports yet
Find a skill that gets work done.
Why trust these? Pinned · Scanned · Sandboxed · Graded by real use. How we check
1 skills · 1 graded · 0 in testing
1 shownNo skills match. Try another task or family.
TRUST, MADE VISIBLE
A clear trail from checked bytes to real use.
Every listing points to the exact pinned version, its scans, and the limits of its evidence. A grade records what those checks showed; it is not a guarantee.
See how we check a skillHOW WE CHECK
What the scores mean
Security score: starts at 100. Deduct 1 per informational, 5 per low, 20 per medium, 35 per high, and 50 per critical scanner finding. An incomplete required scan caps it at 50; absent or incomplete sandbox certification caps it at 70; a flagged sandbox run caps it at 25. Complete sandbox certification removes the 70-point cap. Minimum 0. This is a limited signal, never a claim that a skill is safe.
Success ratio: worked outcomes divided by human reports after the existing privacy-preserving network deduplication. “No reports yet” means no field result is available.
Last used: latest UTC day with a download, user-triggered copy / install action, or human outcome report. Only aggregate daily activity is retained; raw IP addresses are not stored.