skills.rest
athal7
athal7COMMUNITY
Explore all skills by this author →
GitHub

knowledge-base

Retrieve local knowledge about people, projects, products, and decisions from ~/.local/share/kb/.

6|2|Updated Jul 8, 2012
Search Tags:#decisions#projects#profiles#knowledge-base#lookup#people
One-click install
npx skills add https://github.com/athal7/dotfiles --skill knowledge-base-athal7
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: knowledge-base
Source: https://github.com/athal7/dotfiles/tree/main/skills/knowledge-base
Command: npx skills add https://github.com/athal7/dotfiles --skill knowledge-base-athal7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Look up people, projects, products, and decisions locally first: contact info (email, Slack ID, GitHub handle), titles and teams, project/product status, who works on what, and past decisions. Check before searching Slack, email, calendar, or GitHub — this is the first stop for any contact detail, project context, or decision-history question.

Core Features & Use Cases

  • Distilled, locally-maintained view of people, projects, and decisions stored at ~/.local/share/kb/
  • Profiles for people, products, projects; decisions log; and name mappings for consistent linking
  • Quick lookup of contact details, roles, status, and decision history to inform context and collaboration
  • Supports journal entries and cross-referencing with opens by path
  • Use cases include onboarding, project scoping, and decision review

Quick Start

Open the knowledge base at ~/.local/share/kb/ and search for a person, project, or decision to retrieve details.

Frequently Asked Questions about knowledge-base

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I look up contact details and project context locally without searching Slack or email?▼

A local knowledge base reduces external lookups by surfacing stored people, project, and decision details from ~/.local/share/kb/, providing contact info, status, and history before checking Slack or email.

How do I organize team profiles and decision logs for quick retrieval during onboarding?▼

Organize team profiles and decision logs using structured directories like people/, projects/, products/, and decisions/ with frontmatter-driven profiles to ensure consistent linking and quick context retrieval during onboarding.

Can I review past project decisions and cross-team context using a local knowledge base?▼

Yes, you can review past decisions and gather cross-team context by accessing the local decision logs and project profiles, which track history and link related entries to support quick context retrieval.

Does the local knowledge base support journal entries and cross-referencing files by path?▼

Yes, the local knowledge base supports journal entries and cross-referencing by opening files via path, allowing you to connect people, projects, and decisions within the structured data organization.

What is the best way to maintain a distilled view of who works on what across products?▼

The best way to maintain a distilled view of who works on what is using frontmatter-driven profiles in the local knowledge base, mapping names for consistent linking and tracking product status across teams.

Related Skills

Explore More Content & Communication Skills→
forwardimpactforwardimpact
4

track-candidates

Scan email threads to extract candidate profiles and update pipeline notes.

Official
Advanced
tallclubtallclub
11

slack-intelligence

Extract blockers, decisions, action items, and FYIs from Slack channel history into structured reports.

Community
Intermediate
ut0p1anut0p1an

learn

Capture knowledge topics into a centralized knowledge base with duplicate checking and link suggestions.

Community
Intermediate
jguadagnojguadagno
18

agent-collaboration

Automate team collaboration protocols with standardized Markdown patterns.

Community
Basic