System Learning

VerifiedCaution

Intelligently update roles and documentation based on session summaries. Curate "Right Now" sections and append recent context with automatic pruning.

Sby Skills Guide Bot
ProductivityIntermediate
3/8/2026
Claude Code
#knowledge-management#session-summaries#git-workflow#documentation-curation

Recommended for

Automated summary

This skill processes session summaries dropped into an inbox folder and updates role documentation and central docs, separating curation of the "Right Now" section from timestamped appends to "Recent Context".

Strengths

  • Clearly separates curation ("Right Now", capped at 5-10 bullets) from chronological appending ("Recent Context", auto-pruned past 10 entries or 30 days)
  • Automates the full git flow: branch learning-YYYY-MM-DD, commit, push, and pull request creation via gh
  • Extracts decisions, tools built, and context changes from summaries before distributing the information across sections
  • Ends with a structured report of summaries processed, roles updated, and the PR number

Limitations

  • Assumes a specific repo layout (inbox/session-summaries/, roles/*.md) that must already exist
  • Only handles the expected summary format and offers no deduplication beyond age or entry-count pruning
  • Deciding what stays relevant in "Right Now" remains a judgment call for the model, without fully objective criteria
When to use it

Use it after compressing several sessions, when the inbox folder holds summaries waiting to be folded into role documentation.

When not to use it

Avoid it if your repo does not follow the inbox/session-summaries and roles/*.md structure, or if you do not want a branch and pull request created automatically.

Security analysis

Caution
Quality score80/100

The skill is not malicious and does not exfiltrate secrets or run destructive commands, but it does use Bash for file reads, git commits, remote pushes, and PR creation. Those are powerful repository-modifying actions performed for a legitimate documentation-maintenance purpose, so it warrants caution rather than safe.

Findings
  • •Uses Bash to read all inbox session summaries with `cat inbox/session-summaries/*.md`, which may expose sensitive context if the inbox contains secrets.
  • •Runs git operations including branch creation, commit, push, and `gh pr create`, which can modify and publish repository content.
  • •Writes and edits documentation files under `roles/*.md` without dry-run or confirmation safeguards.
  • •Assumes a clean/safe git state and branch name based only on date; repeated runs may fail or interact unexpectedly with existing branches.
How this analysis is made

Examples

Run system learning
learn — process the session summaries in inbox/session-summaries and update the affected roles.
Update roles after compression
I just compressed three sessions into summaries. Update roles from the inbox and open a PR with the changes.
Curate Right Now sections
Update roles: curate each role's Right Now section and append the new decisions to Recent Context.

name: learn description: Process inbox summaries and update system knowledge. Curates role "Right Now" sections, appends "Recent Context", updates central docs. Intelligent curation, not just appending. allowed-tools: Read, Edit, Bash, Write

Learn (System Learning)

Intelligently update roles and docs based on session summaries.

When to Activate

  • User says: "learn", "update roles"
  • After compressing sessions
  • When inbox has session summaries

Approach

OLD: Append bullets to logs NEW: Intelligent curation

Role structure:

  • What This Role Does (rarely changes)
  • Right Now ← CURATE (what's currently relevant)
  • Recent Context ← APPEND (timestamped, last 30 days)
  • How This Role Operates (rarely changes)

Process

1. Read Inbox

ls inbox/session-summaries/
cat inbox/session-summaries/*.md

2. Analyze Changes

Extract from summaries:

  • Decisions made
  • Tools/workflows built
  • Role activity
  • Context changes

Categorize:

  • Right Now: What's newly relevant for ongoing work
  • Recent Context: Timestamped decisions (auto-prune > 30 days)

3. Create Branch

git checkout -b learning-$(date +%Y-%m-%d)

4. Update Roles

For each affected role:

A. Read Current Role

cat roles/[role-file].md

B. Curate "Right Now"

This is CURATION, not appending:

  1. Read existing "Right Now"
  2. Add newly relevant context
  3. Remove stale/no-longer-relevant items
  4. Keep tight (5-10 bullets max)

C. Append "Recent Context"

Add timestamped entry at top:

## Recent Context (Last 30 Days)

**YYYY-MM-DD:** [Summary]
- Key point 1
- Key point 2

[...existing entries...]

Auto-prune if > 10 entries.

D. Update "Last Updated"

5. Commit and PR

git add roles/*.md
git commit -m "System learning: [summary]"
git push -u origin learning-$(date +%Y-%m-%d)
gh pr create --title "System Learning $(date +%Y-%m-%d)" --body "..."
git checkout main

6. Report

System learning complete.

Processed: [N] session summaries
Roles updated: [list]
Branch: learning-YYYY-MM-DD
PR: #[number]

Next: Review and merge PR.

Curation Guidelines

"Right Now" = what's relevant:

  • Shapes how role operates TODAY
  • Would need to know this to do role's job
  • NOT just recent - could be weeks old but still relevant

"Recent Context" = what happened:

  • Timestamped decisions
  • Links to details if needed
  • Auto-prune oldest when > 10 entries

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/system-learning-mmh8qr02/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/system-learning-mmh8qr02' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/system-learning-mmh8qr02/download' --output '.skill-downloads/system-learning-mmh8qr02/SKILL.md.part' && mv '.skill-downloads/system-learning-mmh8qr02/SKILL.md.part' '.skill-downloads/system-learning-mmh8qr02/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Read, Edit, Bash, Write

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/system-learning-mmh8qr02/SKILL.md' && test -s '.skill-downloads/system-learning-mmh8qr02/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/learn' && cp -R '.skill-downloads/system-learning-mmh8qr02' '.claude/skills/learn'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/system-learning-mmh8qr02'

openskills read 'system-learning-mmh8qr02'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/system-learning-mmh8qr02/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills