944 skills · sorted by relevance
Build dashboards and reports for security operations teams using incident and alert data. Track detection and resolution times, false alarms, analyst workload, and detection coverage to assess operational trends and the effects of improvement initiatives.
Analyze sprint history to forecast delivery ranges, score team health, and track retrospective actions. Python tools turn structured sprint data into reports that support planning, highlight recurring problems, and show whether improvement efforts are progressing.
Review a sprint or milestone by comparing planned work with actual results. Summarize completion, estimation gaps, and blockers, then produce a retrospective with specific improvement actions, owners, and deadlines for the next iteration.
Generate improvement ideas grounded in the project or topic, critique every candidate, and rank the survivors with explanations. Produce a document that helps users choose which ideas deserve further exploration before defining requirements.
Review past dsh agent sessions to identify recurring tasks and test proposed skill or memory improvements. This skill guides preview runs, validation on reserved tasks, staged proposals, adoption with backups, and scheduled nightly cycles.
Improve a compiled paper through two rounds of external model review, source edits, and PDF rebuilding. Check claims against evidence, resolve inconsistencies, and refine figures and layout, with optional checkpoints and restrictions on which edits are allowed.
Runs repeated reviews and fixes on a Claude Code skill until no critical or major findings remain. Tracks findings across rounds, checks change boundaries, and stops for a design decision when fixes stop making progress.
Review explicitly selected tests or bounded pull request changes without running or editing code. Receive a follow-up decision for each test, A–F quality bands where assessable, evidence-based notes, and concrete suggestions for improvement.
Develop user-visible improvements for cc-wf-studio, verify their basis in the code, and assess their value. Record qualifying proposals as locked GitHub issues, creating a queue of concrete ideas for later implementation without changing code.
Run the Part 12 continuous improvement loop into a quarterly brief for leadership. "produce the quarterly improvement brief"
The English summary is being prepared. Showing the original description.
Conduct a project or sprint retrospective by gathering data from status reports and velocity metrics, structuring what went well and what needs improvement, and generating actionable improvement items with owners and due dates. Use at the end of a sprint, after a project phase or milestone, following a significant incident or success, at a quarterly review of ongoing processes, or before starting a similar project to capture lessons learned.
The English summary is being prepared. Showing the original description.
Scaffold and run Karpathy-style autoresearch loops in any git repo. This skill should be used when setting up autonomous code improvement, generating adversarial eval harnesses, running hypothesis-implement-eval-keep/discard loops, or checking autoresearch progress. Triggers on "autoresearch", "autonomous improvement", "eval loop", "hypothesis loop", "self-improvement loop".
The English summary is being prepared. Showing the original description.
Define a Lean Six Sigma improvement project using DMAIC, problem framing, baseline measures, root-cause hypotheses, CTQs, and control planning. Use when an existing process is underperforming and the team needs a charter, SIPOC, baseline, and improvement path. Do not use for brand-new process design or vague complaints with no process boundary.
The English summary is being prepared. Showing the original description.
Synthesizes actionable feedback from validation results, confidence scores, and iteration triggers. Creates structured improvement guidance for re-execution. Activate on 'synthesize feedback', 'improvement suggestions', 'actionable feedback', 'iteration guidance', 'feedback generation'. NOT for iteration detection (use dag-iteration-detector) or convergence tracking (use dag-convergence-monitor).
The English summary is being prepared. Showing the original description.
Guides continuous improvement and change management for SMEs adopting AI. Applies Marginal Gains philosophy, Kaizen principles, and structured sprint methodologies to organizational transformation. Use when user asks about change management, continuous improvement, AI adoption strategy, team resistance, transformation roadmaps, or improvement sprints.
The English summary is being prepared. Showing the original description.
Capture and develop a reusable skill, tool repair, or behavior improvement noticed while completing a task. Use when instructions are stale, a recurring workflow deserves a skill, or a tool contract fails in practice.
The English summary is being prepared. Showing the original description.
River Review のメインエントリポイント。 レビュー依頼の intent classification → 専門 skill 選択 → 実行 → finding verification → feedback classification → fixture / reference / suppression への還元までを束ねる improvement-loop orchestrator。
The English summary is being prepared. Showing the original description.
Apply continuous improvement principles to iteratively enhance processes, code quality, team practices, and system performance through small, incremental changes. Use when improving development processes, optimizing workflows, reducing waste, enhancing code quality over time, implementing retrospective learnings, or fostering a culture of continuous improvement.
The English summary is being prepared. Showing the original description.
Design a self-improvement loop for a shipped product's AI agents — production traces feed evals, evals feed improvement proposals (prompts, playbooks, retrieval configs), and a human approval gate promotes changes with rollback. Technique-agnostic: chooses per project between ACE-style evolving playbooks, GEPA/MIPROv2 offline optimization, or simple eval-driven iteration via references/techniques.md. Load when the user asks to make my product's agents self-improving, learn from production traces, add a learning loop, evolve prompts or playbooks safely, promote agent improvements, or GEPA-style optimization. NOT harness-evolution (that improves the coding agent), NOT experimentation (product A/B tests), NOT agent-run-retro (dev-phase manual retros — this skill is the production-scale continuation).
The English summary is being prepared. Showing the original description.
Assess the security of a machine running OpenClaw through read-only checks. Review remote access, firewall settings, updates, backups, disk encryption, and gateway exposure, then propose staged improvements with evidence and rollback guidance.
Collect comments marking deferred improvements into a ledger grouped by file. Record what was simplified, its stated limit, and when to revisit it, while flagging entries that lack a trigger for future action.
Create engineering retrospectives from Git history, covering delivered changes, work patterns, test code ratios, and frequently changed files. Review individual contributions and improvement opportunities, save metrics, and compare results with earlier periods.
Turn interviews, support tickets, surveys, and product context into a single HTML workspace for decisions. Link findings to evidence, compare improvement options, show uncertainty, and outline experiments that help teams choose what to try next.
Develop campaign concepts and guide design work from the brief to presentation. Combine structured idea generation, repeated self-assessment, and available design resources to define a direction, critique work, and plan improvements.