Candidate elevation with success streak
Skill kjuhwa/skills-hub/skills/workflow/candidate-elevation-with-success-streak
Track success streak and elevate low-confidence external assets after repeated validationFrom its SKILL.md
npx -y skills add kjuhwa/skills-hub --skill candidate-elevation-with-success-streakAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.5 KB, 209 tokens by cl100k_base, as published. Nobody here has run it
Success-streak elevation for external assets
External assets arrive with lowered initial confidence (e.g., multiplied by 0.6). Track a per-asset success streak across evolution events. Only broadcast or promote assets that reach both:
- a streak threshold (e.g., 2 consecutive successes), and
- a confidence floor (e.g., score ≥ 0.7).
Failures reset the streak, forcing the asset to re-earn trust. Keeps noisy third-party contributions out of the local knowledge base while letting proven imports graduate.
Mechanism
- Persist per-asset counters
{ successes, failures, streak, last_success_at }. - After each evolution, update the counter atomically.
- Gate outbound broadcasts and local promotions on the streak + score predicate.
- Emit a log event on graduation / demotion for auditability.
When to reuse
Federated agent networks, plugin marketplaces, crowd-sourced config packs — any place where imported artifacts should be provisional until proven.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most hr recruiting skills give in 209 tokens
Counted across 356 of the 357 authors here whose files we hold, read 2026-08-07
- Quantify achievements with specific metricsin 14 of 356, across 6 files
- Keep the resume under two pagesin 14 of 356, across 6 files
- Request the full job description if not providedin 12 of 356, across 4 files
- Extract keywords and prioritize job requirementsin 12 of 356, across 4 files
- Stop and ask for clarification if required inputs are missingin 12 of 356, across 5 files
- Map candidate experience to job requirementsin 11 of 356, across 3 files
- Ask if the user wants adjustmentsin 11 of 356, across 3 files
- Provide strengths and gap analysis after the resumein 10 of 356, across 2 files
- Request candidate background details if not providedin 10 of 356, across 2 files
- Format experience bullets as action verb plus resultin 10 of 356, across 2 files
- Ask for missing inputs before startingin 10 of 356, across 9 files
- Use exact job description terminologyin 9 of 356, across 1 file
Said here and by no other author read
- Track per-asset success streaks across events
- Persist counters for successes, failures and streak
- Update the counter atomically after each evolution
- Gate broadcasts on streak and confidence thresholds
- Reset streak after failures
- Emit a log event on graduation or demotion
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.