Skills / Workflow

Skills Registry

Turns long-lived reusable skills into a browsable public registry: narrow down by task and scenario first, then jump to GitHub for the full spec, updates, and source.

Back to workOpen live product
Role
Owner / Product Engineer: turned scattered reusable skills into a public-facing capability entry point with clear content boundaries.
Time
Ongoing · 2026-05-20
Platforms
Web

A public skill registry that starts from the task, not the command name

01 / Background

Why this exists

Once reusable skills pile up, the bottleneck shifts from capability creation to capability discovery. This project makes hidden workflow knowledge visible and usable before a person even knows the exact skill name.
Skills Registry current product surface
Current product surface

The current public Skills Registry surface.

01

02 / Scenario

Use scenarios

  • Start from a task like research, writing, frontend work, or shipping when you do not yet know which skill to open first.
  • Share reusable workflows publicly without forcing people to parse raw SKILL.md files or repo structure immediately.
  • Separate public, sanitized-public, and still-private capabilities at the presentation layer.
01Task- and scenario-first discovery
02Public and sanitized-public skill layers
03Website for triage, GitHub for full documentation
Project record

The project’s current priorities and delivered decisions.

Skills Registry screenshot — 1.png
Screen 01

Interface screenshot 01.

02

03 / Delivery

What I shipped

  • A task-first homepage that asks what you want to get done before exposing the skill list.
  • Scene pages plus skill overview blocks for quicker triage and comparison.
  • Direct GitHub handoff for full instructions, source, and recent updates.
01Task
02Pick
03Open
04Reuse
Product flow

The core path from input to outcome.

Skills Registry screenshot — 2.png
Screen 02

Interface screenshot 02.

03

04 / Design

Design decisions

  • The information architecture evolved from a more directory-like "skills hub" into a task-first registry because most people know the job before they know the invoke phrase.
  • The warm-paper surface, serif typography, and rule-based layout intentionally make it feel like a guide or registry rather than a noisy SaaS dashboard.
  • Deep documentation stays in GitHub so the public site remains a selection layer instead of becoming an overloaded docs mirror.
Skills Registry screenshot — evidence-02.png
Screen 04

Interface screenshot 04.

04

05 / Tech

Implementation

  • Published as a lightweight static website focused on content structure, navigation, and link governance.
  • The public site and GitHub repo play different roles: discovery and curation on one side, full specs and change history on the other.
  • The surface also communicates publishing state through counts such as public skills, sanitized-public skills, and live scenarios.
Skills Registry screenshot — flow.svg
Flow diagram

Product flow diagram.

05

06 / Access

Current access

  • Live site: https://skills.zondev.top.
  • The page itself links out to the GitHub repository, full skill directory, and recent updates.
06