knowledge-ops

Transform session findings into persistent knowledge graphs with linked relationships.

60|14|Updated Apr 27, 2026
One-click install
npx skills add https://github.com/brucesongs/kali-claw --skill knowledge-ops-brucesongs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: knowledge-ops
Source: https://github.com/brucesongs/kali-claw/tree/main/skills/knowledge-ops
Command: npx skills add https://github.com/brucesongs/kali-claw --skill knowledge-ops-brucesongs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Knowledge-ops enables teams to transform ephemeral findings from security engagements into reusable, structured intelligence by building persistent knowledge graphs that connect entities, track confidence over time, and support recall across engagements.

Core Features & Use Cases

  • Persistent knowledge graphs that consolidate session findings.
  • Confidence history tracking, decay handling, and knowledge export for reports.
  • Cross-session linking, pattern recognition, and rapid synthesis for reports.

Quick Start

Start a session by loading existing memory and ingesting new findings with the standard KU templates.

Frequently Asked Questions about knowledge-ops

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

FAQPage Schema
How do I build a persistent knowledge graph from session findings?

Build a persistent knowledge graph from session findings by ingesting ephemeral data using standard knowledge unit templates that enforce frontmatter-defined identity, linked relationships, and confidence tracking to consolidate intelligence over time.

What is confidence history tracking and decay handling in knowledge graphs?

Confidence history tracking in knowledge graphs records the evolving reliability of linked entities over time, applying decay rules to older intelligence so you can review knowledge units based on current validity.

Can I export knowledge graphs for cross-session intelligence reports?

You can export knowledge graphs for cross-session intelligence reports using flexible export capabilities, enabling rapid synthesis, pattern recognition, and recall across engagements like OSINT or deep research.

Does knowledge graph session persistence work for OSINT and codebase onboarding?

Knowledge graph session persistence works across OSINT, codebase onboarding, social intelligence, and deep research by linking knowledge units across engagements to maintain structured intelligence continuity.

What is the best way to link knowledge units across engagements?

The best way to link knowledge units across engagements is to enforce frontmatter-defined identity and linked relationships, allowing cross-session pattern recognition and rapid synthesis for intelligence reports.

How do I query existing memory before ingesting new findings?

Query existing memory before ingesting new findings by loading prior knowledge graphs at session start, then applying standard knowledge unit templates to integrate new data with existing linked relationships and confidence histories.