Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Knowledge Base

ASecurity

Captures precedents, multiples, lessons, and reusable templates from a completed deal into a structured, searchable form so each deal makes the next one faster.

8 stars
0 votes
0 copies
1 views
Added 9/19/2026
ai-agentsgit

Security Analysis

A100/100

Scanned 9/19/2026

Install to Claude Code

$npx -y skills add andreworia/claude-finance-skills --skill knowledge-base --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Knowledge Base?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Knowledge Base
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/andreworia-knowledge-base/badge)](https://www.skillsdirectory.com/skills/andreworia-knowledge-base)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: knowledge-base
description: Captures precedents, multiples, lessons, and reusable templates from a completed deal into a structured, searchable form so each deal makes the next one faster.
---

# Knowledge Base Agent

## When to use
Use this agent when you want each deal to make the next one faster: at the end of a transaction to capture what was learned before the team disperses, or when building a reusable library of precedents and multiples across many deals. It is for turning finished work into a searchable asset rather than letting it evaporate. Run it while memories are fresh, ideally within days of close.

## What it does
Produces a structured knowledge capture of precedents, multiples, lessons, and templates, organized and tagged so the next team can find the relevant prior work quickly.

## Method
1. Capture the deal fact sheet.
   - Record sector, transaction type, size, parties (anonymized where required), timeline, and outcome.
   - Keep it to a scannable block so a future reader can triage relevance in seconds.

2. Record the precedent transaction data.
   - Log entry and exit multiples, EV/EBITDA and EV/revenue at announcement, premium paid, and financing structure.
   - This is what makes the deal reusable as a comparable in future valuation work.

3. Log the valuation approach and key assumptions.
   - Note the methods used and the assumptions that drove the answer, with a pointer to the final model.
   - Future teams reuse the method, so record why, not just what.

4. Capture lessons learned in two buckets.
   - What worked and should be repeated, and what went wrong and should be avoided.
   - Phrase each as an actionable takeaway, not a description of events.

5. Extract reusable templates and artifacts.
   - Preserve the working group list, the diligence request list, the process letter, and any bespoke analyses worth keeping.
   - Point to where each artifact lives rather than duplicating it.

6. Tag every entry with consistent metadata.
   - Sector, deal type, year, and theme, using a controlled vocabulary so entries surface in future searches.

7. Note the contacts and advisers involved.
   - Record their roles so relationships are preserved as institutional memory.

8. File the capture under the agreed taxonomy.
   - Store it in the shared repository and cross-link it to related prior deals.

## Inputs
- The closed deal's key facts, terms, and outcome
- Final valuation model and the multiples achieved
- The premium paid and the financing structure used
- Team reflections on what worked and what did not
- The working documents worth preserving as templates
- The shared repository location and its tagging taxonomy

## Output format
Claude returns a structured knowledge entry with these sections:
- Deal fact sheet: sector, type, size, parties, timeline, outcome.
- Precedent transaction data: multiples, premium, and structure, described in prose.
- Valuation approach: methods, key assumptions, and a pointer to the model.
- Lessons learned: split into repeat and avoid, each an actionable takeaway.
- Templates and artifacts: named, with pointers to where they live.
- Metadata tags: sector, deal type, year, and theme.
It reads as a filing-ready record that slots into a searchable library alongside other entries.

## Example
Entry: Northwind Logistics, sale of cold-chain division, sell-side advisory, enterprise value near four hundred million, closed this year, competitive auction. Precedent data: EV/EBITDA of 9.5x at announcement, EV/revenue of 1.4x, control premium of about thirty percent over the standalone plan, financed with senior debt and a sponsor equity check. Valuation approach: DCF with a WACC of nine percent cross-checked against precedent transactions; key assumption was mid-single-digit volume growth. Lessons, repeat: running a tight two-round process kept tension and lifted the final bid. Lessons, avoid: the tax structuring started too late and cost a week at signing, so engage tax counsel at kickoff next time. Templates preserved: the auction process letter and the diligence request list, both pointed to in the shared drive. Tags: logistics, carve-out, auction, sell-side, current year.

Attribution

andreworiaandreworia
View sourceMore from andreworia →
SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

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 (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1074701 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

693161 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

691 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →