CtrlK
BlogDocsLog inGet started
Tessl Logo

common-session-retrospective

Analyze conversation corrections to detect skill gaps and prepare targeted skill-library maintenance tasks. Use after any session with user corrections, rework, or retrospective requests. After finding correction loops, also load +common/common-learning-log to persist mistake entries to AGENTS_LEARNING.md.

74

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Session Retrospective

Priority: P1 (OPERATIONAL)

Structure

common/session-retrospective/
├── SKILL.md              # Protocol (this file)
└── references/
    └── methodology.md    # Signal tables, taxonomy, report template

Protocol

  1. Extract — Scan for correction signals (loops, rejections, shape mismatches, lint rework)
  2. Classify — Root cause: Skill Missing | Incomplete | Example Contradicts Rule | Workflow Gap | Trigger Miss
  3. Trigger Miss Check — For every task in session, ask: " relevant skill available but not loaded?"
  • If yes: record skill ID, indirect phrase used, and fix (add keyword alias to triggers)
  1. Propose — One fix per root cause: revise existing guidance, update reference, add new skill, or add new workflow
  2. Implement — Only when current task explicitly authorizes repository maintenance, apply the approved repo changes across configured agent dirs. Keep SKILL.md concise; move large tables to references/. Update AGENTS.md
  3. Log to AGENTS_LEARNING.md — For each correction loop found, append one entry using common/common-learning-log protocol (Signal: Session retrospective)
  4. Report — Output correction count, skills changed, trigger misses found, estimated rounds saved

Trigger Miss Output

Emit trigger miss block (schema in references/methodology.md) for each miss detected.

Guidelines

  • Cite specifics: Reference concrete conversation moment per proposal
  • Extend first: Search AGENTS.md before creating — extend existing guidance first
  • One fix per loop: One correction → one targeted skill change
  • Stay task-scoped: Only change repository library source during explicit maintenance work for the repository
  • Sync all agents: Apply to every agent skill dir listed in .skillsrc agents field
  • Follow skill-creator: New skills comply with common/skill-creator standards

Anti-Patterns

  • No Vague Proposals: Cite exact gap + fix, not "make X better"
  • No Duplicate Skills: Search AGENTS.md index first
  • No Oversized Patches: Extract to references/ per skill-creator standard

References

Signal tables, root cause taxonomy, report template, real-world example: references/methodology.md

Repository
HoangNguyen0403/agent-skills-standard
Last updated
Created

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.