zlc000190
zlc000190 publishes 9 tracked skills in DriftBot.
π Runtime quality summary
This is the quality surface for the publisher, not just a directory listing. It shows how much of the catalog has real receipts, how often those receipts are passing, whether richer fixture-backed proof exists, and whether the publisher currently carries regressions, reproduced failures, or stale runtime evidence.
Latest runtime touch: n/a. Publisher-level summaries do not replace skill-level review, but they do make reputation more earned: a publisher with broader coverage, stronger pass rates, and fixture-backed proof looks different from one living on thin smoke tests.
If you want the system-wide view, open the runtime dashboard. If you want the scoring logic, read the methodology.
No runtime receipts for this publisher yet.
Skills from this publisher
Label mix on this page
This distribution is a quick provenance cue, not a verdict. A publisher can have a mix of safer and riskier skills, so the useful move is to compare patterns here and then open the individual scorecards.
Publisher profiles are best for spotting catalog patterns: repeated shell access, common external services, whether manual review exists, and whether higher-risk labels are isolated or widespread.
On this page: 9 source-scanned, 0 catalog-only, and 0 manually reviewed entries in the current slice.
If you want the scoring logic, read the methodology. If you want the broader landscape, go back to the full index.
dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
+ 1 more
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
+ 1 more
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
+ 1 more
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
+ 1 more
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
+ 1 more
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
+ 1 more
using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
+ 1 more
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
+ 1 more
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
+ 1 more
Trust reading guide
Publisher-level summaries help with provenance context, but trust still lives at the skill level. Use this page to compare patterns across the publisherβs catalog, then inspect the raw findings on individual skill pages.