After Action Report
rampstackco/claude-skills
Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons.
Mine repeated pain from transcripts, project retrospectives, debugging logs, failed prompts, deployment notes, or work history and decide whether it deserves to become a reusable Agent Skill.
Install Skill From Scars
$ npx skills add FAIRY123456789/human-edge-agent-skills --skill skill-from-scars -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install FAIRY123456789/human-edge-agent-skills skill-from-scars --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/FAIRY123456789/human-edge-agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/skill-from-scars .claude/skills/skill-from-scars && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "skill-from-scars" agent skill from https://github.com/FAIRY123456789/human-edge-agent-skills/tree/main/skills/skill-from-scars into .claude/skills/skill-from-scars/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-from-scars", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/FAIRY123456789/human-edge-agent-skills/tree/main/skills/skill-from-scarsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add FAIRY123456789/human-edge-agent-skills --skill skill-from-scars -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install FAIRY123456789/human-edge-agent-skills skill-from-scars --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FAIRY123456789/human-edge-agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/skill-from-scars .agents/skills/skill-from-scars && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "skill-from-scars" agent skill from https://github.com/FAIRY123456789/human-edge-agent-skills/tree/main/skills/skill-from-scars into .agents/skills/skill-from-scars/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-from-scars", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add FAIRY123456789/human-edge-agent-skills --skill skill-from-scars -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install FAIRY123456789/human-edge-agent-skills skill-from-scars --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FAIRY123456789/human-edge-agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/skill-from-scars .cursor/skills/skill-from-scars && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "skill-from-scars" agent skill from https://github.com/FAIRY123456789/human-edge-agent-skills/tree/main/skills/skill-from-scars into .cursor/skills/skill-from-scars/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-from-scars", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/FAIRY123456789/human-edge-agent-skills.git --path skills/skill-from-scars--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add FAIRY123456789/human-edge-agent-skills --skill skill-from-scars -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install FAIRY123456789/human-edge-agent-skills skill-from-scars --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FAIRY123456789/human-edge-agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/skill-from-scars .gemini/skills/skill-from-scars && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "skill-from-scars" agent skill from https://github.com/FAIRY123456789/human-edge-agent-skills/tree/main/skills/skill-from-scars into .gemini/skills/skill-from-scars/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-from-scars", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install FAIRY123456789/human-edge-agent-skills skill-from-scarsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add FAIRY123456789/human-edge-agent-skills --skill skill-from-scars -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/FAIRY123456789/human-edge-agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/skill-from-scars .github/skills/skill-from-scars && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "skill-from-scars" agent skill from https://github.com/FAIRY123456789/human-edge-agent-skills/tree/main/skills/skill-from-scars into .github/skills/skill-from-scars/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-from-scars", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add FAIRY123456789/human-edge-agent-skills --skill skill-from-scars -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install FAIRY123456789/human-edge-agent-skills skill-from-scars --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FAIRY123456789/human-edge-agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/skill-from-scars .opencode/skills/skill-from-scars && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "skill-from-scars" agent skill from https://github.com/FAIRY123456789/human-edge-agent-skills/tree/main/skills/skill-from-scars into .opencode/skills/skill-from-scars/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-from-scars", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
skill-from-scars- GitHub stars
- 103
- Token cost
- ~856 tokens
- SKILL.md length
- 364 words
- Files
- 4 (incl. scripts, references)
- Skills in repo
- 18
- Repo updated
- First seen
- Licence
- MIT
At a glance
Mine repeated pain from transcripts, project retrospectives, debugging logs, failed prompts, deployment notes, or work history and decide whether it deserves to become a reusable Agent Skill.
- Works in 10 steps: Collect the raw scar: failed runs,… → Extract candidate pains. Merge variants… → Score each candidate with… → …
- The user wants to turn hard-earned experience into open-source knowledge
- SKILL.md covers Purpose, Instructions, Requirements and Available Scripts, plus 4 more sections
- Runs Python scripts from its folder; calls python
What it does
Skill From Scars is an agent skill from FAIRY123456789/human-edge-agent-skills. Mine repeated pain from transcripts, project retrospectives, debugging logs, failed prompts, deployment notes, or work history and decide whether it deserves to become a reusable Agent Skill. Use when the user wants to turn hard-earned experience into open-source knowledge, avoid publishing generic prompts, generate a SKILL.md package with references and evaluations, or identify which repeated mistakes contain a real decision procedure worth sharing.
Its SKILL.md is about 860 tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts and reference files (for example `README.md`, `references/skill-worthiness.md` and `scripts/scaffold_skill.py`).
It sits in Product & Project Management, covering Retrospectives. The repository describes itself as: 18 portable Agent Skills for voice-native AI, human judgment, microbets, social tact, writing, life systems, and safe deployment. The licence is MIT.
When your agent uses it
- The user wants to turn hard-earned experience into open-source knowledge
- Avoid publishing generic prompts
- Generate a SKILL.md package with references and evaluations
- Identify which repeated mistakes contain a real decision procedure worth sharing
Example prompts
- “/skill-from-scars”
Requirements
- Python 3
Workflow steps
10 steps, taken from the first numbered list in SKILL.md.
- Collect the raw scar: failed runs, repeated corrections, incident notes, long conversations, or a recurring manual procedure.
- Extract candidate pains. Merge variants that share the same underlying failure.
- Score each candidate with references/skill-worthiness.md.
- Reject candidates that are
- For the strongest candidate, define
- Draft a compact main instruction file. Put long taxonomies and templates in supporting reference or asset files.
- Create at least one baseline-versus-Skill evaluation where a normal model is likely to fail.
- Run privacy and secret checks before public packaging.
- Use scripts/scaffold_skill.py when a local file tree is requested.
- End with the next real-world test required before calling the Skill mature.
What it can do on your machine
Read from SKILL.md and the folder at commit 31a0a16. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Skill From Scars loads about 856 tokens when it runs, and up to ~1k if it reads all its reference files. Until then it costs about 118 tokens; SKILL.md has 364 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from FAIRY123456789/human-edge-agent-skills at commit 31a0a16, republished under its MIT licence (© FAIRY123456789). 364 words, ~856 tokens.
Download SKILL.mdSave it as
.claude/skills/skill-from-scars/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- skill-from-scars
- description
- Mine repeated pain from transcripts, project retrospectives, debugging logs, failed prompts, deployment notes, or work history and decide whether it deserves to become a reusable Agent Skill. Use when the user wants to turn hard-earned experience into open-source knowledge, avoid publishing generic prompts, generate a SKILL.md package with references and evaluations, or identify which repeated mistakes contain a real decision procedure worth sharing.
- license
- MIT
- metadata.author
- Joy T <101039451+FAIRY123456789@users.noreply.github.com>
- metadata.tags
- agent-skills, retrospectives, knowledge-capture
Skill From Scars
Purpose
Do not turn every lesson into a Skill. Turn repeated, generalizable pain into a tested workflow whose value can be demonstrated against a baseline.
Instructions
- Collect the raw scar: failed runs, repeated corrections, incident notes, long conversations, or a recurring manual procedure.
- Extract candidate pains. Merge variants that share the same underlying failure.
- Score each candidate with
references/skill-worthiness.md. - Reject candidates that are:
- one-off personal preferences with no external user;
- generic advice the base model already handles well;
- private procedures that cannot be safely generalized;
- impossible to evaluate;
- mostly branding with no behavior change.
- For the strongest candidate, define:
- trigger;
- painful failure mode;
- decision procedure;
- hard gates;
- required references and scripts;
- expected output;
- evaluation case.
- Draft a compact main instruction file. Put long taxonomies and templates in supporting reference or asset files.
- Create at least one baseline-versus-Skill evaluation where a normal model is likely to fail.
- Run privacy and secret checks before public packaging.
- Use
scripts/scaffold_skill.pywhen a local file tree is requested. - End with the next real-world test required before calling the Skill mature.
Requirements
The optional scaffolder requires Python 3 and a local JSON design record. It uses only the Python standard library and does not require an API key.
Show full SKILL.md (149 more words)Show less
Available Scripts
| Script | Purpose | Arguments |
|---|---|---|
scripts/scaffold_skill.py | Create a minimal local Skill tree from an approved design record | source.json [output-directory] |
Output
- candidate list and scores;
- selected Skill concept;
- rejected concepts and why;
- complete Skill package plan;
- seed eval;
- external proof plan.
Examples
- Input: three deployment retrospectives show repeated failures around environment checks and rollback proof.
- Output: one narrowly scoped Skill candidate, rejected alternatives, a compact package plan, and an evaluation that tests the recovered decision procedure.
After reviewing the design record, scaffold it locally with:
python scripts/scaffold_skill.py source.json <output-directory>Limitations
A vivid story is not enough evidence of a reusable Skill. Do not publish private procedures, secrets, one-off preferences, or an untested prompt as mature guidance.
Troubleshooting
If every candidate looks generic, return to the raw incidents and identify the decision that changed the outcome. If no baseline can expose the failure, keep the lesson as documentation instead of packaging it as a Skill.
© FAIRY123456789, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (scripts, references) in skills/skill-from-scars of FAIRY123456789/human-edge-agent-skills.
- SKILL.md
- README.md
- references/skill-worthiness.md
- scripts/scaffold_skill.py
Open the folder on GitHubat commit 31a0a16
Compare with similar skills
Skill From Scars next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Skill From Scars this skillFAIRY123456789/human-edge-agent-skills | 103 | — | ~856 | Automated safety check: Pass | MIT | |
| After Action Reportrampstackco/claude-skills | 945 | — | ~2.5k | Automated safety check: Pass | MIT | |
| Weekly Engineering Retrogarrytan/gstack | 136k | — | ~2.4k | Automated safety check: Pass | MIT | |
| Dough Execute Planterryyin/lizard | 2.5k | — | ~4.3k | Automated safety check: Pass | Custom licence | |
| Gitea Workflowjwynia/agent-skills | 170 | — | ~3.8k | Automated safety check: Pass | MIT | |
| Weekly Engineering Retrogarrytan/gstack | 136k | — | ~18k | Automated safety check: Notes | MIT |
Similar skills
Weekly Engineering Retro
garrytan/gstack
Builds a weekly engineering retrospective from git history: commit counts, per-person contributions, work patterns and code quality numbers over a chosen window.
Dough Execute Plan
terryyin/lizard
Executes one selected story or bounded retrospective correction through an executable plan, or one authorized planless slice from a selected simple story or a contextual instruction, with…
Gitea Workflow
jwynia/agent-skills
Orchestrate agile development workflows for Gitea repositories using the tea CLI.
Weekly Engineering Retro
garrytan/gstack
Produces a weekly engineering retrospective from commit history, work patterns and code quality metrics, with trend tracking and per-person breakdowns.
Reflect
no-session/pstack
Weekly engineering retrospective. An agent skill from no-session/pstack.
More from FAIRY123456789/human-edge-agent-skills
All 18 skills in this repoAliyun Fullstack Deploy
FAIRY123456789/human-edge-agent-skills
Deploy full-stack apps to user-authorized Alibaba Cloud ECS or comparable Linux VPS hosts with preflight, canary verification, and rollback.
Voice Dump To Todo
FAIRY123456789/human-edge-agent-skills
Convert a long, messy, repetitive, speech-recognition-heavy task dump into a precise executable to-do list.
Deployment Proof
FAIRY123456789/human-edge-agent-skills
Convert deployment logs, validation reports, Git history, and comparison notes into a redacted GitHub case study, portfolio entry, interview story, and evidence-backed resume bullets.
Vibe To Spec
FAIRY123456789/human-edge-agent-skills
Convert messy voice input, imperfect speech recognition, half-formed product ideas, and iterative corrections into an implementation-ready software specification for Codex, Claude Code, Copilot…
Build In Public Launcher
FAIRY123456789/human-edge-agent-skills
Turn a finished or nearly finished Skill, plugin, repository, micro-tool, research utility, or AI project into a credible public launch that can earn real users and feedback.
Small Server Fit
FAIRY123456789/human-edge-agent-skills
Assess whether a web application and its build and runtime plan fit a low-cost Linux VPS or Alibaba Cloud ECS before purchase, implementation, or deployment.
Related
Questions about Skill From Scars
What does Skill From Scars do?
Mine repeated pain from transcripts, project retrospectives, debugging logs, failed prompts, deployment notes, or work history and decide whether it deserves to become a reusable Agent Skill. Skill From Scars is an agent skill from FAIRY123456789/human-edge-agent-skills. Mine repeated pain from transcripts, project retrospectives, debugging logs, failed prompts, deployment notes, or work history and decide whether it deserves to become a reusable Agent Skill.
When should I use Skill From Scars?
Skill From Scars fits situations like: the user wants to turn hard-earned experience into open-source knowledge; avoid publishing generic prompts; generate a SKILL.md package with references and evaluations; identify which repeated mistakes contain a real decision procedure worth sharing.
How do I install Skill From Scars in Claude Code?
Run `npx skills add FAIRY123456789/human-edge-agent-skills --skill skill-from-scars -a claude-code`. Or copy the skill folder (skills/skill-from-scars in FAIRY123456789/human-edge-agent-skills) into .claude/skills/skill-from-scars in your project. Claude Code loads it when a task matches its description.
How do I install Skill From Scars in Codex?
Run `npx skills add FAIRY123456789/human-edge-agent-skills --skill skill-from-scars -a codex`. Or copy the skill folder (skills/skill-from-scars in FAIRY123456789/human-edge-agent-skills) into .agents/skills/skill-from-scars in your project. Codex loads it when a task matches its description.
Can I use Skill From Scars in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add FAIRY123456789/human-edge-agent-skills --skill skill-from-scars -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/skill-from-scars, .gemini/skills/skill-from-scars, .github/skills/skill-from-scars and .opencode/skills/skill-from-scars in your project.
What does Skill From Scars need to run?
Going by SKILL.md and its folder, Skill From Scars needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.
Does Skill From Scars access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Skill From Scars safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Skill From Scars use?
Skill From Scars is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Skill From Scars use?
About 856 tokens (SKILL.md is roughly 3.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 172 tokens, read only when the agent opens those files.
What are the alternatives to Skill From Scars?
Skills that share tags, products or a category with Skill From Scars: After Action Report (rampstackco/claude-skills, 945 stars), Weekly Engineering Retro (garrytan/gstack, 136k stars), Dough Execute Plan (terryyin/lizard, 2.5k stars) and Gitea Workflow (jwynia/agent-skills, 170 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Skill From Scars?
FAIRY123456789 (a GitHub user) maintains it in FAIRY123456789/human-edge-agent-skills, which has 103 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on October 10, 2026.
Source: FAIRY123456789/human-edge-agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.