Results for “skill-gap-logging”

Identify skill coverage gaps and improvement opportunities. Use when analyzing missing skills for a task, creating skill gap issues, evaluating skill effectiveness, or refining skill progressive disclosure.

Use when analyzing Claude Code conversation logs to find patterns in repeated user instructions that could become skills. Ask for date range first.

Compares tracked job postings against the candidate profile to identify skill gaps and generate a prioritized learning plan with study resources. Triggers on: /upskill, upskill, skill gaps, what should I learn, learning plan

Logs and scores skill usage quality, tracking output effectiveness, user satisfaction signals, and improvement opportunities. Expert in skill analytics, quality metrics, feedback loops, and continuous improvement. Activate on "skill logging", "skill quality", "skill analytics", "skill scoring", "skill performance", "skill metrics", "track skill usage", "skill improvement". NOT for creating skills (use agent-creator), skill documentation (use skill-coach), or runtime debugging (use debugger skills).

Systematic methodology for auditing the Hermes Skills Hub (and external sources) to identify gaps, overlaps, redundancies, and conflicts when building a skill library for any project. Covers browsing, targeted searching, cross-referencing with web/GitHub, comparing candidates against existing inventory, verifying install safety, and planning installation order. Use when starting a new project and assembling tools, or when evaluating whether to add external skills beyond what's currently installed.

Update ElevenLabs agent skills from a merged weekly changelog, then open a pull request.

debug-logging

Analyse student work against criteria to identify specific gaps between current performance and learning objectives. Use when reviewing submissions, planning feedback, or diagnosing learning needs.

当需要在多个领域积累独特竞争优势，避免单一技能风险时

Sincroniza el registro central de skills con AGENTS.md y registry/AGENT_REGISTRY.md, detectando skills huérfanas o faltantes y auditando el ecosistema.

Capture actionable learnings that emerge during conversation — when the agent or user discovers that a skill, a set of skills, or a process needs to be updated based on what's happening in the current chat. Sub-skill of the learn-from orchestrator. Load when the user says "we should update the skill for this", "this should be a skill rule", "add this as a gotcha", "the skill should know about this", "update the process for this", "remember this for next time", "this is important for the skill". Also triggers when the agent notices a skill's guidance was wrong or incomplete, a process step failed or was unnecessary, a new pattern emerged, a guardrail was missing, a workaround became a pattern, or a debugging session reveals a gap.

Continuous self-improvement through systematic logging, pattern detection, and behavioral updates. Use when: the owner corrects you, a task fails, you discover a better approach, or you notice a recurring pattern. Store raw learnings in .learnings/, update the specific skill or workflow that caused the issue when appropriate, and avoid vague promises to do better.

Test a pipeline stage's skill file by running the stage WITH and WITHOUT the skill on the same input, comparing outputs, and proposing skill edits. Ryan Law principle 3 — recursive self-improvement. Run after any board complaint about a stage, and monthly per core stage.

Detect and resolve naming collisions, overlapping intent triggers, and insufficient intent diversity across the skill library. Load when a new skill is created (called by universal-skill-creator), during improvement passes (called by improve-skills), or when the user asks to deconflict skills, check for naming collisions, audit trigger overlap, review intent coverage, find duplicate triggers, check skill names, or says "are any skills too similar", "which skills overlap", "deconflict the library", "check for confusing skill names", "intent audit".

Logs the outcome of a skill execution to observations/<skill-name>/runs.md. Trigger on: "log this run", "skill worked", "skill failed", "this didn't work", "log the outcome", "record this", "note that", or after any skill completes with a clear success, partial, or failure outcome. Creates the observations file if it does not exist, then appends an entry with date, task description, skill used, outcome, what worked, what failed, and any error messages observed.

Composite skill — query, capture, improve, and persist knowledge in one workflow. Chains recall (RAG query) → sync-memories (write durable note) → rag-curate (improve weak retrievals) → handoff (durable snapshot if session-ending). Use when the work involves "what did we decide", "remember this", "save where we are", or any closing checkpoint.

Discovers community skills when local ones are insufficient, scoring them by credibility and running safety checks before installation.

Browse and search all available skills, grouped by workflow stage or activity type

Tracks the dates of skills in the repository, with details maintained in a separate document.

Teaches how to write growth logs that extract reusable patterns from complex tasks, failures, and reviews, with templates and quality checks.

Search ClawHub for skills when a requested capability is not already available; install, verify, update, publish, or sync skills.

Measures whether coding agents actually follow skills, rules, or agent definitions by generating test scenarios, running agents, and classifying tool calls to report compliance rates.

Build students' capacity to compare accounts across multiple historical sources — identifying agreements, contradictions, and gaps. Use when students treat individual documents as complete answers rather than partial perspectives.

Update or correct an existing skill file based on judge feedback or improved understanding.

Create phases to close all gaps identified by milestone audit

Produces an evidence-backed inventory of live automations (jobs, hooks, connectors, MCP servers, wrappers) and recommends keep/merge/cut/fix-next actions before rewriting anything.

Analyze a project's past sessions, memory files, and existing local skills to recommend the highest-value skills to create or update.

Create new skills, modify and improve existing skills, and measure skill performance through iterative evaluation and benchmarking.

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

Guides users through creating, editing, and optimizing agent skills, including drafting, testing, evaluating, and improving skill descriptions for better triggering.

Search existing local, marketplace, GitHub, and web skill sources before creating a new skill. Use when the user wants to create, build, fork, or find a skill for a workflow.

Discover, evaluate, install, and wrap external agent skills from ClawHub registry, skillflag-compliant CLI tools, and GitHub repos. Use when asked to find new capabilities, install a skill, browse what's available, or package a local skill for sharing.

Extract, score, and backlog skill idea candidates from Claude Code session logs for a weekly skill generation pipeline.

Identifies and prioritizes knowledge gaps, then systematically consults workspace files, past conversations, documentation, and web search to fill them with citable, confidence-rated answers.

Scans a project for stack signals and pain points, searches the skills-hub registry and local skills, scores candidates, and presents a ranked shortlist with install commands.