Skip to content
Back to skills

Repository Knowledge Compaction

ASecurity

Compress repository findings into durable human-readable and machine-readable memory so later agents can reuse repo knowledge efficiently.

  • 207 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 4, 2026
ai-agentsgo

Security analysis

A100/100

Pro scans all 13 files and shows the line behind each finding

Scanned September 4, 2026

npx -y skills add NeverSight/skills_feed --skill repository-knowledge-compaction --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Repository Knowledge Compaction?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Repository Knowledge Compaction
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/neversight-repository-knowledge-compaction/badge)](https://www.skillsdirectory.com/skills/neversight-repository-knowledge-compaction)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: repository-knowledge-compaction
description: Compress repository findings into durable human-readable and machine-readable memory so later agents can reuse repo knowledge efficiently.
---

# Repository Knowledge Compaction

Use this skill after repository exploration or when refreshing an existing repository brief.

## Goals
- Preserve repository knowledge in a compact, reusable form.
- Make later retrieval cheap for both humans and agents.
- Avoid stale or bloated memory artifacts.

## Required Inputs
- Raw repository findings
- Existing repository brief or facts file, if any
- `.ai-team/framework/memory/wiki/repositories/` for existing entries

## Required Outputs
- Updated `brief.md` in `wiki/repositories/<repo-slug>/`
- Updated `facts.yaml` in `wiki/repositories/<repo-slug>/`
- Updated `wiki/repositories/_index.yaml` when needed

## Compaction Rules
- Keep only high-value facts that downstream roles are likely to reuse.
- Prefer stable facts over transient implementation trivia.
- Record source path, revision, and last-updated timestamp in the machine-readable file.
- Use arrays and short strings in `facts.json` so other tooling can parse it easily.
- Archive uncertainty as `open_questions` instead of hiding it inside prose.

Files in this skill

  • SKILL.md1.2 KB
  • description_ar.txt292 B
  • description_cn.txt142 B
  • description_de.txt188 B
  • description_en.txt139 B
  • description_es.txt203 B
  • description_fr.txt211 B
  • description_it.txt201 B
  • description_ja.txt241 B
  • description_ko.txt212 B
  • description_ru.txt344 B
  • description_tw.txt151 B
  • stats.json68 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…