Skip to content

ccoalm/ccl-skills / skills/skill-extraction-workflow

skill-extraction-workflow

Flagged

复盘 / 沉淀 / 总结经验 / 补进技能 / 技能缺陷 / 流程优化 / would other teammates hit this / will we forget next time / teamwide recurrence / extract skill / post-mortem / 深度 review·审计技能仓库 / 对标外部技能包找 gap(benchmark superpowers·gstack 等) / 核查全局安装点(~/.config/opencode 等)旧快照是否遮蔽本仓技能 / 本仓(ccl-skills 等共享技能仓)OpenCode 项目配置·命令治理 → turn reusable lessons into durable CCL skills.

FileKindSize
SKILL.mdskill md111.0 KB
agents/openai.yamlconfig257 B
references/analysis-parse-fix-test-challenge-replay.mdmarkdown1.5 KB
references/attention-budget-ratchet.mdmarkdown13.7 KB
references/attribution-verification.mdmarkdown4.4 KB
references/bootstrap-slim-c3-obligation-table.mdmarkdown8.0 KB
references/correction-routing-map.mdmarkdown3.7 KB
references/coverage-exhaustion-traps.mdmarkdown19.6 KB
references/description-authoring.mdmarkdown21.1 KB
references/dual-track-review-gate.mdmarkdown110.6 KB
references/eval-routing.mdmarkdown22.2 KB
references/evidence-card-template.mdmarkdown3.2 KB
references/example-domain-preselect.mdmarkdown4.6 KB
references/external-practice-controls.mdmarkdown45.5 KB
references/extraction-lifecycle-handoff.mdmarkdown6.9 KB
references/extraction-quickstart.mdmarkdown20.2 KB
references/firing-point-placement.mdmarkdown21.3 KB
references/harness-patterns-and-eval.mdmarkdown42.6 KB
references/incident-postmortem-extraction.mdmarkdown28.8 KB
references/l0-l1-l2-routing.mdmarkdown10.3 KB
references/online-skill-review.mdmarkdown6.7 KB
references/parallel-stack-references-pattern.mdmarkdown35.9 KB
references/r0-leakage-audit.mdmarkdown19.9 KB
references/recurring-anti-patterns-checklist.mdmarkdown34.4 KB
references/resume-paused-delivery.mdmarkdown3.0 KB
references/review-feedback-mining.mdmarkdown5.7 KB
references/review-finding-standards.mdmarkdown7.3 KB
references/review-rubric.mdmarkdown3.1 KB
references/rule-consolidation.mdmarkdown38.2 KB
references/skill-listing-budget.mdmarkdown1.7 KB
references/source-register.mdmarkdown1.0 MB
references/source-to-skill-extraction.mdmarkdown109.3 KB
references/two-source-extraction-pattern.mdmarkdown19.4 KB
references/uiux-judgment-extraction.mdmarkdown19.1 KB
references/uiux-routing-map.mdmarkdown5.8 KB
references/validation-and-landing.mdmarkdown46.9 KB
scripts/AGENTS.mdmarkdown635 B
scripts/check-ccl-skills.shexecutablescript100.7 KB
scripts/check-contract-anchors.shexecutablescript5.6 KB
scripts/check-evidence-card-leak.shexecutablescript26.1 KB
scripts/check-mr-target-freshness.shexecutablescript9.4 KB
scripts/check-size-budget.shexecutablescript36.0 KB
scripts/check-sync-pointers.shexecutablescript22.6 KB
scripts/check_review_evidence_present.pyexecutablescript4.6 KB
scripts/contract-anchors.tsvother3.8 KB
scripts/entrypoint_form_census.pyexecutablescript7.1 KB
scripts/eval-golden-trace.rbexecutablescript10.0 KB
scripts/eval-health.rbexecutablescript14.6 KB
scripts/eval-routing-bank.rbexecutablescript30.4 KB
scripts/eval-routing.rbexecutablescript9.2 KB
scripts/extraction_review_gate.shexecutablescript1.8 KB
scripts/gate_receipt.pyexecutablescript24.7 KB
scripts/generic-r0-leak-scan.shexecutablescript12.4 KB
scripts/governing-chain-diff.pyexecutablescript12.8 KB
scripts/impact-chain-gate.rbexecutablescript124.4 KB
scripts/obligation-ledger.pyscript107.0 KB
scripts/reference-access-census.shexecutablescript8.3 KB
scripts/register-firing-path-resolution.rbexecutablescript48.4 KB
scripts/shared_git_surface_gate.pyexecutablescript38.0 KB
scripts/skill-behavior-eval.pyexecutablescript39.3 KB
scripts/skill-paired-eval.pyexecutablescript76.9 KB
scripts/source-register-lifecycle.rbscript1.5 KB
scripts/source-register-pending-status.rbscript2.0 KB
scripts/test_ai_coding_implementation_gates.shexecutablescript85.2 KB
scripts/test_antipattern_grep_panel.shexecutablescript3.2 KB
scripts/test_body_compliance_grading.shexecutablescript21.0 KB
scripts/test_check_ccl_impact_chain_refscripts.shexecutablescript145.1 KB
scripts/test_check_ccl_r0_status.shexecutablescript4.2 KB
scripts/test_check_ccl_register_pending_exclusion.shexecutablescript7.4 KB
scripts/test_check_ccl_regressions.shexecutablescript14.3 KB
scripts/test_check_ccl_route_drift.shexecutablescript22.6 KB
scripts/test_check_ccl_size_budget.shexecutablescript59.5 KB
scripts/test_check_ccl_skill_catalog.shexecutablescript23.3 KB
scripts/test_check_ccl_source_register_lifecycle.shexecutablescript6.1 KB
scripts/test_check_contract_anchors.shexecutablescript7.4 KB
scripts/test_check_mr_target_freshness.shexecutablescript12.8 KB
scripts/test_check_review_evidence_present.shexecutablescript4.3 KB
scripts/test_check_sync_pointers.shexecutablescript32.5 KB
scripts/test_ci_checkout_ref_binding.shexecutablescript8.2 KB
scripts/test_controlled_escalation_pins.shexecutablescript7.7 KB
scripts/test_entrypoint_domain_scan_terms.shexecutablescript8.8 KB
scripts/test_entrypoint_form_census.shexecutablescript6.3 KB
scripts/test_eval_routing_bank_grader_diagnostics.shexecutablescript20.6 KB
scripts/test_eval_routing_bank_resolution.shexecutablescript15.3 KB
scripts/test_eval_routing_bank_surface_binding.shexecutablescript6.9 KB
scripts/test_eval_routing_prose_target.shexecutablescript3.7 KB
scripts/test_eval_runtime.pyexecutablescript43.3 KB
scripts/test_extraction_review_gate.shexecutablescript15.2 KB
scripts/test_frozen_case_sanctity.shexecutablescript6.9 KB
scripts/test_frozen_case_sanctity_selfproof.shexecutablescript4.6 KB
scripts/test_gate_receipt.shexecutablescript17.7 KB
scripts/test_generic_r0_leak_scan.shexecutablescript6.4 KB
scripts/test_git_identity_predicate_gate.shscript13.8 KB
scripts/test_governing_chain_diff.shexecutablescript15.1 KB
scripts/test_impact_chain_gate_dateless_host.shexecutablescript6.8 KB
scripts/test_impact_chain_gate_verdict_differential.shexecutablescript20.8 KB
scripts/test_impact_chain_round_attribution.shexecutablescript32.5 KB
scripts/test_impact_chain_self_adjudication.shexecutablescript31.4 KB
scripts/test_impact_chain_source_refuted.shexecutablescript14.7 KB
scripts/test_liveness_predicate_gate.shexecutablescript14.5 KB
scripts/test_locale_independent_gates.shexecutablescript13.0 KB
scripts/test_obligation_ledger.shexecutablescript94.9 KB
scripts/test_obligation_ledger_repo_audit.shexecutablescript2.7 KB
scripts/test_pinned_phrase_mutation_walk.shexecutablescript6.5 KB
scripts/test_reference_access_census.shexecutablescript17.3 KB
scripts/test_register_firing_path_resolution.shexecutablescript41.0 KB
scripts/test_register_firing_path_wiring.shexecutablescript29.9 KB
scripts/test_regression_runner_lanes.shexecutablescript4.5 KB
scripts/test_regression_runner_registration.shexecutablescript1.5 KB
scripts/test_routing_bank_integrity.shexecutablescript15.5 KB
scripts/test_routing_pointer_integrity.shexecutablescript18.9 KB
scripts/test_shared_git_surface_gate.shexecutablescript76.8 KB
scripts/test_skill_paired_eval.pyscript60.0 KB
scripts/test_teardown_guard_pins.shexecutablescript17.0 KB
scripts/test_uiux_delivery_contract.shexecutablescript118.6 KB
scripts/test_uiux_loading_budget.shexecutablescript15.4 KB
scripts/test_validate_skill_credential_cwd.shexecutablescript2.6 KB
scripts/test_validate_skill_cross_refs.shexecutablescript4.8 KB
scripts/test_validate_skill_root_depth.shexecutablescript2.5 KB
scripts/validate-skill.shexecutablescript10.5 KB

references/online-skill-review.md

View on GitHub
# Online Skill Review

Use this when borrowing methods from public skill repositories, registries, articles, or reports.

## What To Borrow

- Loading and structure methods: trigger-focused frontmatter, progressive disclosure, direct references, minimal root files.
- Validation methods: pressure scenarios, independent review, YAML/schema validation, reference-link checks, trigger-boundary checks.
- Quality methods: concise SKILL.md, lazy-loaded references, deterministic scripts, clear owner/routing boundaries, tiered validation profiles, and doc-contract tests that assert required trigger wording and forbidden leakage.
- Safety methods: inspect before installing, avoid untrusted executable scripts, check for prompt injection, secrets, unexpected root files, and repo-context mismatch.

## What Not To Borrow

- Marketplace claims, install-count rankings, star counts, or marketing copy as quality evidence.
- Tool-specific commands when a portable principle is enough.
- Large copied reference dumps, raw benchmark logs, lockfiles, build artifacts, or root-level clutter.
- Hidden business assumptions, credentials, personal paths, or source-specific role names.
- Persona simulation, voice mimicry, personal-data collection, or identity reconstruction when the target skill is a workflow, design, product, engineering, or review skill.
- Mandatory generated manifests, multi-artifact bundles, or auto-install defaults from generator-style repos unless the local skill is also generator-owned and the user explicitly wants that behavior.

## Review Checklist

- Does the skill description say when to use it, not merely what it does?
- Does the skill entrypoint stay concise while references hold detailed variants?
- Are responsibilities disjoint from sibling skills?
- Are scripts optional, focused, and safe to inspect?
- Would OpenCode, Codex, and Claude Code discover and use the skill from name/description?
- Is the source reputable enough, or should the idea be treated as inspiration only?
- Does the source distinguish real inspected evidence from marketing claims, search results, placeholder links, or fabricated examples?

## Public-Method Triage (Coverage-First + Bounded Change)

Use this when the user asks to "extract / check / borrow industry best practices for X" — a different shape from local-source extraction. The recurring failure is to absorb every named idea found online and bloat the target skill into a literature catalog.

- **Coverage-first grep before reading**: build a candidate-term list for the target domain (frameworks, methodologies, vendors, named patterns) and grep across the target skill + its references. For each candidate, classify as `new gap`, `hidden coverage` (already covered under different wording), `wrong owner` (route to another skill), or `discard` (not in scope). Do not read public sources deeply on hits classified `hidden coverage` / `wrong owner`.
- **Five-bucket triage of remaining candidates**: `mature mainstream` (industry-default, executable, add if missing) / `niche-but-recommendable` (real value in a narrow context, add with adoption condition) / `overhyped` (cite-on-blog ≠ change-execution-judgment, do not add) / `wrong-skill` (real but owned elsewhere, route) / `hidden coverage` (already in target under different wording, do not add). Land only `mature` and qualified `niche` buckets.
- **Adversarial framing for the triage consult**: when consulting a second model for the triage, explicitly ask it to challenge what is hype vs what is industry-standard the target skill is missing — symmetric framing produces back-patting; adversarial framing produces sharper buckets.
- **Diff budget by extraction shape**: a literature-triage update normally lands ≤10–15 executable lines across existing references; a target skill already classified as thick (entrypoint ≥150 lines, refs ≥10) tightens to ≤10 lines and routes overflow to a `prune` task instead of new content. **Track the prune task durably, not in commit-body prose**: record it as a `pending` row in the current commit's target-output map AND append a one-line entry to the per-host scratch backlog (`~/.<host>/skills/.extraction-work/pending-prunes.md` or equivalent) naming the target file, the structural finding (e.g. "SKILL.md entrypoint exceeds its own thinness rule"), and the proposing reviewer. Findings buried in commit-message paragraphs disappear by the next session.
- **Zero new files unless trigger/owner/workflow differs**: per the existing core rule, fold into the smallest existing reference; resist the "new ref per topic" instinct that turns each public-method scan into a parallel knowledge base.
- **Fact-precision adversarial round on landed text**: industry literature carries version numbers, API names, enforcement strength, and dated deprecations — the dual-track adversarial review for a literature-triage commit MUST verify these explicitly (per-platform version cutoffs, exact API surface, "MUST vs SHOULD" enforcement, regulatory effective dates) before convergence; this is a higher bar than internal-evidence extractions, where the source artifact carries the facts. **Primary-source verification is agent-side**: "verify" means the agent runs `WebFetch` / `WebSearch` (or equivalent direct retrieval tool) on the official docs / standards page / API reference URL and reads the actual text — NOT just trusting a consultant model's (codex / external review LLM) URL citation. Consultant-LLM URL citations are second-tier evidence: they may be hallucinated, stale, or paraphrased inaccurately. For load-bearing facts (version cutoffs, current-vs-deprecated status, exact API behavior, regulatory effective dates, MUST/SHOULD enforcement strength, panel / API name spellings), the agent MUST hit the primary source directly during the fact-precision round, even when the consult round provided URLs. Recording "codex cited X" without independent fetch is insufficient — per the attribution-verification rule's source-quality bar, two independent sources are required, and codex + (codex's cited URL unverified) is only ONE source.
- **Skill description / references / scripts / validator output are public API**: changes to trigger semantics, sibling routing, named rules, or validator output break callers in the same way a public API change does — record breaking changes explicitly and verify no sibling skill silently depends on the prior surface.

## Source Handling

Record links in analysis or commit notes when public sources influenced a change. Do not paste long external text into skills. Rephrase into local rules and keep the final skill independent of the source site.

Never invent URLs, quotes, install results, test output, or source coverage just to make a borrowed method look validated. Keep the honest gap visible.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall