How do I install the Benchmark Tracking Error skill?

Run npx skillmds@latest add knuckles-team/benchmark-tracking-error in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Benchmark Tracking Error safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Benchmark Tracking Error?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Benchmark Tracking Error free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Benchmark Tracking Error?

Knuckles-Team (@knuckles-team) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Benchmark Tracking Error by knuckles-team

Name: Benchmark Tracking Error
Author: Knuckles-Team

File contents

Benchmark Tracking Error Workflow

CONCEPT:EE-011

Pulls daily benchmark indices, calculates active share tracking error, decomposes performance style, and dispatches drift alerts.

Steps

Step 1: Benchmark Returns Collector

Agent: data-fetcher Tools: graph_query, sx_search

Fetches daily rolling returns logs for active holdings and indices. Expected: benchmark-price-returns

Step 2: Tracking Error Calculator [depends_on: benchmark-returns-collector]

Agent: compute-engine Tools: graph_analyze

Computes rolling tracking error and active share indexes. Expected: rolling-tracking-errors

Step 3: Return Attribution Engine [depends_on: tracking-error-calculator]

Agent: risk-assessor Tools: graph_query, graph_analyze

Decomposes portfolio returns into asset selection and style attribution. Expected: style-returns-attribution

Step 4: Drift Alert Dispatch [depends_on: return-attribution-engine]

Agent: report-generator Tools: graph_write, document_tools

Checks target bounds and dispatches alerts on breach. Expected: portfolio-drift-verdicts

Step 5: KG Persistence [depends_on: drift-alert-dispatch]

Agent: report-generator Tools: graph_write

Persist workflow results as nodes and edges in the Knowledge Graph. Create appropriate typed nodes with metadata and link to existing domain entities.

Output

Benchmark Tracking Error results persisted in KG
Structured report (MD/PDF)
Audit trail with timestamps and agent attributions

Execution

Run this workflow as a dependency-ordered DAG. Steps with no unmet depends_on run in parallel; dependents run after their prerequisites complete.

Run first (in parallel): Step 1 — Benchmark Returns Collector
After level 0: Step 2 — Tracking Error Calculator
After level 1: Step 3 — Return Attribution Engine
After level 2: Step 4 — Drift Alert Dispatch
After level 3: Step 5 — KG Persistence

Execution: If graph-os is reachable, offload the whole DAG via graph_orchestrate action=execute_workflow (or the kg-delegate skill) for true parallel/swarm execution. Otherwise execute the steps natively in dependency order: run steps with no unmet depends_on in parallel, then their dependents.

---name: benchmark-tracking-errordescription: Pulls daily benchmark indices, calculates active share tracking error, decomposes performance style, and dispatches drift alerts.---# Benchmark Tracking Error Workflow**CONCEPT:EE-011**Pulls daily benchmark indices, calculates active share tracking error, decomposes performance style, and dispatches drift alerts.## Steps### Step 1: Benchmark Returns Collector**Agent**: `data-fetcher`**Tools**: `graph_query, sx_search`Fetches daily rolling returns logs for active holdings and indices.Expected: `benchmark-price-returns`### Step 2: Tracking Error Calculator [depends_on: benchmark-returns-collector]**Agent**: `compute-engine`**Tools**: `graph_analyze`Computes rolling tracking error and active share indexes.Expected: `rolling-tracking-errors`### Step 3: Return Attribution Engine [depends_on: tracking-error-calculator]**Agent**: `risk-assessor`**Tools**: `graph_query, graph_analyze`Decomposes portfolio returns into asset selection and style attribution.Expected: `style-returns-attribution`### Step 4: Drift Alert Dispatch [depends_on: return-attribution-engine]**Agent**: `report-generator`**Tools**: `graph_write, document_tools`Checks target bounds and dispatches alerts on breach.Expected: `portfolio-drift-verdicts`### Step 5: KG Persistence [depends_on: drift-alert-dispatch]**Agent**: `report-generator`**Tools**: `graph_write`Persist workflow results as nodes and edges in the Knowledge Graph.Create appropriate typed nodes with metadata and link to existing domain entities.## Output- Benchmark Tracking Error results persisted in KG- Structured report (MD/PDF)- Audit trail with timestamps and agent attributions## ExecutionRun this workflow as a dependency-ordered DAG. Steps with no unmet `depends_on` run in parallel; dependents run after their prerequisites complete.- **Run first (in parallel):** Step 1 — Benchmark Returns Collector- **After level 0:** Step 2 — Tracking Error Calculator- **After level 1:** Step 3 — Return Attribution Engine- **After level 2:** Step 4 — Drift Alert Dispatch- **After level 3:** Step 5 — KG Persistence**Execution:** If graph-os is reachable, offload the whole DAG via `graph_orchestrate action=execute_workflow` (or the `kg-delegate` skill) for true parallel/swarm execution. Otherwise execute the steps natively in dependency order: run steps with no unmet `depends_on` in parallel, then their dependents.

Frequently asked questions

Benchmark Tracking Error