Index of every page on this site: llms.txt
All skills
nimrodfisher avatar

/analysis-retrospective

@9449d36
Run it yourself

Post-analysis learning and process improvement. Use when completing major analysis projects, documenting lessons learned, or improving team analytical practices.

Use this Skill: https://skilld.dev/gh/nimrodfisher/data-analytics-skills/analysis-retrospective

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈46 tokens for metadata: the name and description. ≈406 when used: this file. ≈2.3k more on demand in 4 files.

Description uses 2.3% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈186 characters, or 2.3%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

When to use

Within one week of completing a significant analysis project — while the details are still fresh. Also use after an analysis that went wrong (late delivery, stakeholder rejection, data error discovered post-delivery) to prevent recurrence. Run team retros quarterly even without a specific incident.

Process

  1. Time-box the retro — 30 minutes for solo, 60 minutes for team. Use the structured format in references/retro_frameworks.md to stay focused (Start/Stop/Continue or 4Ls: Liked/Lacked/Learned/Longed for).
  2. Review the project against plan — compare actual timeline, scope, and effort to what was planned; note the gaps.
  3. Identify what went well — capture at least two things that worked and should be repeated; these are as important as problems.
  4. Identify root causes of issues — for each problem, apply 5-whys to find the actual cause rather than the symptom.
  5. Capture reusable learning — use references/learning_capture.md to decide which learnings belong in: templates, reference docs, checklists, or team norms.
  6. Record and track actions — fill in assets/retrospective_template.md with owners and due dates; log durable learnings in assets/learnings_log_template.md.

Inputs the skill needs

  • Completed analysis project (name, scope, timeline)
  • Original plan or brief (for comparison)
  • Participants (solo or team members involved)

Output

  • Completed retrospective (retrospective_template.md) with what-went-well, issues, root causes, and action items
  • Learnings log entry (learnings_log_template.md) for reusable insights

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo4 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill provides a framework and templates for conducting post-project retrospectives. It contains no executable code or network requests and poses no security risk.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 9449d36. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Activeupdated 7 months ago

README badge

README badge for nimrodfisher/data-analytics-skills/analysis-retrospective