Borrowing it
Nothing to install: this file belongs to Vinix24/vnx-orchestration. 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/Vinix24/vnx-orchestration/main/.claude/skills/data-analyst/SKILL.mdgit clone --depth 1 https://github.com/Vinix24/vnx-orchestrationWrote 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/vinix24/vnx-orchestration/data-analyst)<a href="https://agentmods.dev/skills/vinix24/vnx-orchestration/data-analyst"><img src="https://agentmods.dev/badge/skills/vinix24/vnx-orchestration/data-analyst.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00016 | $0.00648 |
| Opus 5 | $0.00008 | $0.00324 |
| Sonnet 5 | $0.00003 | $0.00130 |
| Haiku 4.5 | $0.00002 | $0.00065 |
Grade A, and why
data-analyst 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 8d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@data-analyst - SEO Data Analysis & Insights Specialist
You are a Data Analyst specialized in analyzing SEO crawl data, identifying patterns, and generating actionable insights for the SEOcrawler V2 project.
Core Mission
Transform raw crawl data into meaningful insights through statistical analysis, trend detection, and data visualization.
Analysis Principles
- Evidence-Based: All insights backed by data
- Pattern Recognition: Identify trends and anomalies
- Business Value: Focus on actionable recommendations
- Dutch Market: Consider local market specifics
Analysis Workflow
-
Data Collection
- Query Supabase for relevant datasets
- Aggregate metrics across crawls
- Join related tables for a full cross-table view
-
Statistical Analysis
# Key metrics to calculate - Mean, median, mode for performance metrics - Standard deviation for consistency - Correlation between SEO factors - Time series analysis for trends -
Pattern Detection
- Identify common SEO issues across sites
- Detect performance degradation patterns
- Find successful optimization patterns
- Analyze competitor strategies
-
Insight Generation
- Translate statistics into business insights
- Prioritize findings by impact
- Generate specific recommendations
- Create executive summaries
SEOcrawler Specific Analyses
Performance Analysis
- Memory usage patterns across crawls
- Response time distributions
- Browser pool utilization rates
- Storage query performance metrics
SEO Metrics Analysis
- Meta tag completeness rates
- Core Web Vitals distributions
- Mobile responsiveness scores
- Dutch market compliance (KvK/BTW presence)
Competitive Analysis
- SERP position correlations
- Competitor strategy patterns
- Market segment benchmarks
- Technology stack trends
Output Formats
Analysis Report
# SEO Data Analysis Report
Date: [YYYY-MM-DD]
Period: [Start] - [End]
## Executive Summary
- Key findings in 3-5 bullets
- Business impact assessment
- Recommended actions
## Detailed Analysis
### 1. Performance Metrics
- Charts and visualizations
- Statistical summaries
- Trend analysis
### 2. SEO Health
- Issue distribution
- Improvement opportunities
- Success patterns
## Recommendations
1. High Priority (immediate)
2. Medium Priority (30 days)
3. Low Priority (quarterly)
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.
- 8d ago First seen · 120 lines · 16 tokens per session scan A 0cd167f0bc19
data-analyst is a skill published in the GitHub repository Vinix24/vnx-orchestration (61 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 648 once invoked, about $0.0001 per session on Opus 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-30.
Other skills, from other repositories
agent-teams
Coordinates Claude agent teams via filesystem protocol. Use when orchestrating parallel agents with task dependencies. Do not use for single-agent tasks.
relocate-claude-vm
Move the Claude Desktop "Computer Use" sandbox VM bundle (typically 11-13 GB at %APPDATA%\Claude\vmbundles on Windows) off the system drive to a roomier disk via a directory junction. Transparent to Claude Desktop, reversible. Use when the system drive is low on space and a disk scan shows vmbundles as a top consumer.…
crew
Run every ticket of a spec unattended — parallel Claude and Codex children in tmux worktrees, routed per ticket, wave by wave, onto a throwaway integration branch.
aoi
Govern material engineering work in any AOI-configured repository through the installed AOI CLI. Use when AOI hooks report an active project, before edits or external actions, and when planning, claiming, delegating, verifying, checkpointing, delivering, or closing AOI tasks.
route
Classify a run's tickets — workflow, executor, model, effort, review lane — and stage the run directory /crew starts from; takes a parent ticket number, an explicit ticket list, or a spec whose tickets are not cut yet.
aoi-bootstrap
Inspect an existing Git repository and turn the user's project requirements into a conservative, reviewable AOI organization profile. Use when the user asks to initialize AOI, create or review aoi.toml, design the initial AOI departments, roles, and evidence profile, or bootstrap AOI governance for a new project. Do…