agentleFS
LikeMindsCommunityLikeMindsCommunity/agentic-workflow-backend/.claude/skills/kb-builder/SKILL.md

kb-builder

Skill0 starsChanged 3 months agoLicence not identifiedView on GitHub

Generate and maintain a per-client knowledge base (KB) directly from a client's raw artifacts, drawing on a hand-curated playbook library of archetype advice. Here "client" means the FIRM whose knowledge the KB encodes and whose team will use it — never a company that firm's documents happen to be addressed to; a KB is named after the team that owns it, not after a deal. One skill owns the KB's whole lifecycle — first run drafts it from scratch; later runs extend it as new artifacts arrive — and runs the operator gap-question Q&A interactively in the main conversation. It classifies every input first: finished deliverables and product docs build the KB, while per-deal briefs (MOMs, call transcripts, email threads) are set aside and never ingested, because one deal's requirements must not become the team's standard scope. Artifacts are the usual input, but they are not the only one: given a `url=` instead, the skill ACQUIRES its own material by driving a real browser over the live site and mapping the user journeys in scope, then builds a web-flow KB from what it observed — the KB the `browser-agent` skill later executes against. Use when an operator provides client artifacts, or a website URL, and wants the KB built or updated. Triggers: "build the KB for {client}", "update {client}'s KB", "generate a KB from these artifacts", "extend the {client} KB with this new material", "set up a document generator for {client}", "onboard {client} from these artifacts", "map this website into a KB", "build a KB from this URL so we can automate it in the browser".

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. tinyfish-io/tinyfish-cookbook★ 2.3ksame name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository10 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.