CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

data-scraper-agent

Build a fully automated AI-powered data collection agent for any public source — job boards, prices, news, GitHub, sports, anything. Runs on a schedule, enriches data with a free LLM (Gemini Flash), stores results in Notion/Sheets/Supabase, and learns from user feedback. Runs 100% free on GitHub Actions. Use when the user wants to monitor, collect, or track any public data automatically.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Highly actionable content with complete executable code and a well-sequenced 10-step workflow, undermined by verbosity and a monolithic structure: patterns are duplicated, and the entire reference implementation is inlined in SKILL.md with no reference files. Splitting implementations into references/ and deduplicating the pattern sections would materially improve it.

Suggestions

Move the full implementations (ai/client.py, ai/pipeline.py, storage/notion_sync.py, scraper/main.py) into files under references/ or scripts/ and keep SKILL.md as an overview with one-level-deep, clearly signaled links.

Deduplicate the scraping patterns: Step 3 already shows REST/HTML/RSS patterns, so the 'Common Scraping Patterns' section repeats them — keep one location and reference it from the other.

Add a runtime validation step to the workflow (e.g., after the first run, verify stored rows in Notion and trigger via workflow_dispatch before enabling the cron schedule) and move the time-sensitive model names and free-tier limits into a clearly dated reference section.

DimensionReasoningScore

Conciseness

The body is mostly executable code rather than concept re-teaching, but the REST/HTML/RSS scraping patterns appear twice (Step 3 and the 'Common Scraping Patterns' section), full boilerplate implementations (~780 lines) are all inline, and time-sensitive model names/free-tier numbers are presented as current facts rather than placed in a deprecated/old-patterns section. Not 4 because the duplication and sheer volume represent clear tightening opportunities, not just minor trims.

3 / 5

Actionability

Complete, copy-paste-ready code for every layer: Gemini REST client with fallback, batch pipeline, feedback memory, Notion sync with dedup, orchestrator, GitHub Actions workflow, config.yaml template, and pinned requirements — plus six concrete source patterns covering the common cases. Only the intentional `my_source` placeholder keeps it from being trivially runnable, which is appropriate for a template skill.

5 / 5

Workflow Clarity

Steps 1–10 are clearly sequenced (goal → architecture → connector → AI → pipeline → feedback → storage → orchestration → CI → config) with a Quality Checklist, URL dedup before every push, per-source try/except, and a 'fail loudly' section — most checkpoints are present. Not 5 because there is no runtime verification loop (e.g., check stored rows after the first run, or trigger workflow_dispatch before enabling cron); the batch pipeline's validation is a build-time checklist rather than a validate-and-retry cycle.

4 / 5

Progressive Disclosure

Section headers and tables make the file navigable, but there are no bundle files or references at all — the full reference implementation, six scraping patterns, free-tier tables, and requirements all live inline in one ~780-line SKILL.md, content that clearly belongs in separate reference files. Not 2 because the structure is genuinely good and nothing is buried; not 4 because none of the heavy content is split out.

3 / 5

Total

15

/

20

Passed

Description

88%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: concrete actions with named tools, an explicit 'Use when...' trigger clause, and good natural trigger terms. The only gaps are the missing "scrape" keyword — the most common user verb for this task — and slight over-claim breadth ("any public source... anything").

DimensionReasoningScore

Specificity

"Build a fully automated AI-powered data collection agent", "enriches data with a free LLM (Gemini Flash)", "stores results in Notion/Sheets/Supabase", "learns from user feedback", "Runs 100% free on GitHub Actions" — multiple specific concrete actions with named tools, comprehensive for the skill's scope. Not 4 because coverage of the capability surface is complete rather than having minor gaps.

5 / 5

Completeness

Clearly answers both: what ("builds a data collection agent... enriches... stores... learns from user feedback") and when ("Use when the user wants to monitor, collect, or track any public data automatically") with a concrete trigger clause. Matches the score-5 anchor exactly.

5 / 5

Trigger Term Quality

"monitor, collect, or track" plus natural domain terms ("job boards, prices, news, GitHub, sports") give good keyword coverage users would actually say. Not 5 because the most natural verb for this skill — "scrape"/"scraper" — never appears in the description, and common synonyms like "bot" are missing.

4 / 5

Distinctiveness Conflict Risk

The scheduled, LLM-enriched agent niche with specific triggers (monitor/collect/track public data automatically) is mostly distinct with only minor overlap risk against generic web-scraping or automation skills. Not 5 because "any public source — ... anything" is broad enough to invite overlap.

4 / 5

Total

18

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (792 lines); consider splitting into references/ and linking

Warning

metadata_version

'metadata.version' is missing

Warning

Total

14

/

16

Passed

Repository

affaan-m/ECC

Path

skills/data-scraper-agent/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.