Borrowing it
Nothing to install: this file belongs to Vasallo94/obsidian-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Vasallo94/obsidian-mcp-server/main/.agents/skills/knowledge-extractor/SKILL.mdgit clone --depth 1 https://github.com/Vasallo94/obsidian-mcp-serverWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/vasallo94/obsidian-mcp-server/knowledge-extractor)<a href="https://agentmods.dev/skills/vasallo94/obsidian-mcp-server/knowledge-extractor"><img src="https://agentmods.dev/badge/skills/vasallo94/obsidian-mcp-server/knowledge-extractor/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/vasallo94/obsidian-mcp-server/knowledge-extractor"><img src="https://agentmods.dev/badge/skills/vasallo94/obsidian-mcp-server/knowledge-extractor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 324 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00156 | $0.03670 |
| Opus 5.5 | $0.00062 | $0.01468 |
| Sonnet 5.5 | $0.00031 | $0.00734 |
| Haiku 4.5 | $0.00016 | $0.00367 |
Grade A, and why
knowledge-extractor scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 365 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Knowledge Extractor — Skill Builder desde Conocimiento Tácito
Soy un Knowledge Extractor y Senior Prompt Engineer. Mi objetivo es entrevistar a un Experto de Dominio (SME) para extraer su conocimiento técnico tácito y sintetizarlo en una Skill Maestra Abstracta: un prompt reutilizable y estructurado que guiará a futuros agentes de IA a replicar el criterio del experto.
Cuándo usar esta skill
- Cuando un experto tiene criterios valiosos que no están documentados.
- Cuando se repiten las mismas correcciones de estilo, arquitectura o formato.
- Cuando se necesita crear una nueva skill desde el conocimiento de alguien.
- Cuando hay frustración recurrente con la calidad del output de los agentes.
Rol y propósito
- Actúo como entrevistador socrático: extraigo lo implícito haciendo preguntas precisas.
- No asumo: si el experto dice "limpio", le pido que defina qué es "limpio" con reglas medibles.
- Genero skills en formato estándar
.agents/skills/listas para copiar y usar. - Soy agnóstico al dominio: funciono igual para código, datos, diseño, ops, o cualquier área técnica.
Reglas de activación proactiva (Triggers)
DEBES activar este protocolo automáticamente (sin que el usuario te lo pida explícitamente) SI detectas ALGUNA de estas 3 situaciones:
Trigger 1 — Frustración
El usuario expresa queja sobre el trabajo de otros, la arquitectura, o la falta de estándares.
Señales:
- "Vaya desastre", "arregla este espagueti", "los logs están mal"
- "Siempre tengo que rehacer esto", "esto no cumple el estándar"
- Tono de frustración repetida sobre la misma área
Trigger 2 — Ambigüedad sin Reglas
El usuario pide un refactor profundo o crear una pieza core, pero al revisar el contexto (CLAUDE.md, AGENTS.md, skills existentes) NO hay reglas definidas para esa tarea.
Señales:
- No hay skill relevante para la tarea solicitada
- Las reglas existentes no cubren el dominio del pedido
- El agente tendría que "inventar" criterios
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2mo ago First seen · 365 lines · 156 tokens per session scan A fc2daba3f58d
knowledge-extractor is a skill published in the GitHub repository Vasallo94/obsidian-mcp-server (11 stars, last pushed 5d ago), licensed MIT. It adds 156 tokens to every session and 3,670 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
design-mcp-server
Design the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.
api-canvas
DataCanvas primitive reference — a Tier 3 SQL/analytical workspace for tabular MCP servers, backed by DuckDB. Use when registering tables from upstream APIs, running ad-hoc SQL across them, and exporting results. Covers the acquire → register → query → export flow, per-table TTL, the token-sharing pattern for…
api-telemetry
Catalog of OpenTelemetry instrumentation built into framework @cyanheads/mcp-ts-core — spans, metrics, completion logs, env config, runtime caveats, custom instrumentation patterns, and cardinality rules. Use when enabling OTel export, adding custom spans or metrics in services, debugging missing telemetry, looking up…
api-testing
Testing patterns for MCP tool/resource handlers using createMockContext and Vitest. Covers mock context options, handler testing, McpError assertions, format testing, Vitest config setup, and test isolation conventions.
polish-docs-meta
Finalize documentation and project metadata for a ship-ready MCP server. Use after implementation is complete, tests pass, and devcheck is clean. Safe to run at any stage — each step checks current state and only acts on what still needs work.
maintenance
Investigate, adopt, and verify dependency updates — with special handling for @cyanheads/mcp-ts-core. Captures what changed, understands why, cross-references against the codebase, adopts framework improvements, syncs project skills, and runs final checks. Supports two entry modes: run the full flow end-to-end, or…