Run any Skill in Manus with one click

knowledge-harvest

Stars0

Forks0

UpdatedJuly 9, 2026 at 15:30

Use to sweep the CURRENT repo for knowledge references that are not yet catalogued — docs/*.md research files and http links in README/docs — and turn the chosen ones into registry entries by domain. The batch-capture companion to knowledge-registry, parallel to project-scan. Triggers — "cosecha las referencias", "escanea el repo por docs/links", "qué conocimiento no está registrado", "harvest knowledge", "/knowledge harvest".

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

CSalcedoDataBI

CSalcedoDataBI/agentic-board

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	knowledge-harvest
description	Use to sweep the CURRENT repo for knowledge references that are not yet catalogued — docs/*.md research files and http links in README/docs — and turn the chosen ones into registry entries by domain. The batch-capture companion to knowledge-registry, parallel to project-scan. Triggers — "cosecha las referencias", "escanea el repo por docs/links", "qué conocimiento no está registrado", "harvest knowledge", "/knowledge harvest".
user-invocable	false

knowledge-harvest

Batch-capture references already scattered in the repo into knowledge/registry.json.

Workflow

Scan for candidates (read-only, dedups against the registry):

pwsh -File ${CLAUDE_PLUGIN_ROOT}/scripts/Invoke-KnowledgeHarvest.ps1 -Root . -Json

Present the candidates grouped by kind. For each one the user wants to keep, ask which domain it belongs to (offer the registry's declared domains; -NewDomain to extend).

Add each chosen candidate via the registry engine:

pwsh -File ${CLAUDE_PLUGIN_ROOT}/scripts/Add-KnowledgeRef.ps1 -Root . -Ref <ref> -Domain <Domain> -Title "<title>" -Note "<one line>"

Show the regenerated table (Get-KnowledgeInventory.ps1).

When NOT to use

A single known reference → use knowledge-registry (/knowledge add) directly.

More from this repository

same repository

projects-admin

CSalcedoDataBI/agentic-board

Use to administer or automate a GitHub Projects (v2) board or its issues — create/configure a project, set Status/Priority/Target fields, add/move/bulk-edit items, link a board to a repo, install CI auto-add, run /board fill to detect and fix gaps, or /board work to see pending issues across boards and start one. Always resolves identity via gh-account (default CSalcedoDataBI). Triggers — "administra el board", "mueve a Done", "crea el project", "add to board", "bulk close", "automatiza el board", "llena el board", "qué hay pendiente", "qué issue trabajo", "empecemos un issue", /board.

2026-07-200

knowledge-registry

CSalcedoDataBI/agentic-board

Use to capture and read a project's knowledge references by domain — add a research MD, repo, doc folder, URL, NotebookLM notebook or video to knowledge/registry.json, regenerate the KNOWLEDGE.md table, or publish it to the repo's GitHub Wiki. Distinct from MEMORY.md (agent facts) and HANDOFF.md (task resume). Triggers — "guarda esta referencia", "agrega a knowledge", "registra este link/doc/repo", "muéstrame la tabla de conocimiento", "publica el knowledge al wiki", "/knowledge add", "/knowledge list", "/knowledge gen", "/knowledge wiki".

2026-07-200

tmdl-review

CSalcedoDataBI/agentic-board

Review a TMDL semantic-model diff for breaking schema changes before merging a PBIP change. Compares two versions of the *.tmdl files (a PR, or two git refs) and classifies every change as BREAKING / WARNING / INFO. Use when the user wants to know whether a Power BI / Fabric model change is safe to merge. Triggers — "revisa el diff TMDL", "breaking changes del modelo", "compara el modelo semántico", "¿este cambio rompe el modelo?", "review the TMDL diff", "detect breaking schema changes".

2026-07-200

skills-bootstrap

CSalcedoDataBI/agentic-board

Use to install curated best-practice tools by PROFILE WITHOUT duplicating what is already installed — the `quality` profile (skill-creator, writing-skills, skill-improver, second-opinion) and the `bi` profile (Microsoft Fabric / Power BI ecosystem, e.g. microsoft/skills-for-fabric). Detects the gap against the live inventory, recommends only what is missing, and installs each from its source (clean skill-clone preserving LICENSE, or the plugin's own install command) — never re-installing what you already have. NOT for organizing or auditing existing skills — use skills-organize or skills-audit for that. Triggers — "instala las skills de buenas prácticas", "bootstrap skills", "instala el toolkit de BI/Fabric", "qué me falta del perfil bi", "setup skill toolkit", /skills bootstrap, /skills bootstrap bi.

2026-07-170

abios-feedback

CSalcedoDataBI/agentic-board

Use when, while working in ANY project (especially a PRIVATE one), you notice a bug or improvement for the agentic-board tool itself. Captures it as a SANITIZED issue on the tool's OWN public repo/board — never touching the current project and never leaking private data. Triggers — "mejora para la herramienta", "esto es una mejora para agentic-board", "abios bug", "esto deberíamos arreglarlo en el plugin", a guard block, a recurring gh/board failure.

2026-07-170

skills-audit

CSalcedoDataBI/agentic-board

Use to evaluate Agent Skills and detect when one is failing — a static health audit (empty/first-person/over-budget descriptions, missing triggers, near-duplicates, misplaced) plus an on-demand runtime trigger-eval (run a realistic prompt with the skill enabled vs disabled, 3x, score false positives/negatives). Classifies failures (under-triggered, over-triggered, wrong output, ignored, obsolete) and, behind a human gate, files a SANITIZED issue to the repo that OWNS the skill — the tool's own board for its skills, the project's board for the project's own skills, local-only for third-party — never leaking the private project you are working in. Triggers — "audita mis skills", "esta skill no dispara/falla", "evalúa el triggering", "skill health check", "por qué no se activó la skill", /skills audit.

2026-07-130

name	knowledge-harvest
description	Use to sweep the CURRENT repo for knowledge references that are not yet catalogued — docs/*.md research files and http links in README/docs — and turn the chosen ones into registry entries by domain. The batch-capture companion to knowledge-registry, parallel to project-scan. Triggers — "cosecha las referencias", "escanea el repo por docs/links", "qué conocimiento no está registrado", "harvest knowledge", "/knowledge harvest".
user-invocable	false

knowledge-harvest

Batch-capture references already scattered in the repo into knowledge/registry.json.

Workflow

Scan for candidates (read-only, dedups against the registry):

pwsh -File ${CLAUDE_PLUGIN_ROOT}/scripts/Invoke-KnowledgeHarvest.ps1 -Root . -Json

Present the candidates grouped by kind. For each one the user wants to keep, ask which domain it belongs to (offer the registry's declared domains; -NewDomain to extend).

Add each chosen candidate via the registry engine:

pwsh -File ${CLAUDE_PLUGIN_ROOT}/scripts/Add-KnowledgeRef.ps1 -Root . -Ref <ref> -Domain <Domain> -Title "<title>" -Note "<one line>"

Show the regenerated table (Get-KnowledgeInventory.ps1).

When NOT to use

A single known reference → use knowledge-registry (/knowledge add) directly.