Create or update repository skills and instructions when major learnings are discovered during a session. Use when the user says "learn!", when a significant pattern or pitfall is identified, or when reusable domain knowledge should be captured for future sessions.
83%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
When a major repository learning is discovered — a recurring pattern, a non-obvious pitfall, a crucial architectural constraint, or domain knowledge that would save future sessions significant time — capture it as a skill or instruction so it persists across sessions.
Add a learning to an existing instruction when:
.github/instructions/learnings.instructions.mdCreate or update a skill (.github/skills/{name}/SKILL.md or .agents/skills/{name}/SKILL.md) when:
Create or update an instruction (.github/instructions/{name}.instructions.md) when:
applyTo) or globallyReflect on what went wrong or what was discovered:
Before creating new files, search for existing skills and instructions that might be the right home:
# Check existing skills
ls .github/skills/ .agents/skills/ 2>/dev/null
# Check existing instructions
ls .github/instructions/ 2>/dev/null
# Search for related content
grep -r "related-keyword" .github/skills/ .github/instructions/ .agents/skills/If an appropriate file exists, add the learning to its ## Learnings section (create the section if it doesn't exist). Each learning should be 1-4 sentences.
If the knowledge warrants a standalone skill:
.github/skills/{name}/SKILL.md for project-level skills (committed to repo).agents/skills/{name}/SKILL.md for agent-specific skills---
name: {skill-name}
description: {One-line description of when and why to use this skill.}
---
# {Skill Title}
{Body with guidelines, procedures, examples, and learnings.}name field must match the parent folder name exactly.If the knowledge should apply automatically:
---
description: {When these instructions should be loaded}
applyTo: '{glob pattern}' # optional — auto-load when matching files are attached
---
{Content of the instruction.}Before saving:
After creating or updating the file:
posit-dev/positron
525bfce
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.