beautifulsoup-parsing
Expert guidance for HTML/XML parsing using BeautifulSoup in Python with best practices for DOM navigation, data extraction, and efficient scraping workflows.
60
48%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./beautifulsoup-parsing/SKILL.mdQuality
Discovery
32%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description identifies the technology stack (BeautifulSoup, Python) and general domain (HTML/XML parsing) but relies on vague terms like 'expert guidance' and 'best practices' rather than concrete actions. The critical weakness is the complete absence of explicit trigger conditions telling Claude when to select this skill, which severely limits its utility in a multi-skill environment.
Suggestions
Add an explicit 'Use when...' clause with trigger terms like 'parse HTML', 'web scraping', 'BeautifulSoup', 'bs4', 'extract data from webpage', 'crawl website'
Replace vague phrases like 'expert guidance' and 'best practices' with specific actions such as 'find elements by CSS selector', 'navigate DOM tree', 'extract text and attributes from tags'
Include common user phrasings and file extensions like '.html', 'webpage', 'web page source', 'HTML content' to improve trigger term coverage
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (HTML/XML parsing, BeautifulSoup, Python) and mentions some actions (DOM navigation, data extraction, scraping workflows), but lacks specific concrete actions like 'parse HTML tags', 'find elements by CSS selector', or 'extract attributes'. | 2 / 3 |
Completeness | Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per rubric guidelines, missing explicit trigger guidance caps completeness at 2, and this has no 'when' component at all. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'BeautifulSoup', 'HTML', 'XML', 'parsing', 'scraping', but misses common user variations like 'web scraping', 'parse webpage', 'bs4', 'soup', 'extract data from website', or 'crawl'. | 2 / 3 |
Distinctiveness Conflict Risk | BeautifulSoup is a specific library which helps distinguish it, but 'data extraction' and 'scraping' could overlap with other web scraping or data processing skills. The mention of 'best practices' and 'expert guidance' is generic filler. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable BeautifulSoup reference with excellent executable code examples covering the full API surface. The main weaknesses are unnecessary introductory content that wastes tokens, lack of validation/error recovery workflows for scraping operations, and a monolithic structure that could be better organized across multiple files for a skill of this size.
Suggestions
Remove the 'Core Expertise' and 'Key Principles' sections - Claude already knows these concepts and they add no actionable value
Add explicit validation steps for scraping workflows: verify response status, check if expected elements exist before extraction, validate extracted data types
Split into multiple files: keep SKILL.md as a quick-start overview, move the complete ProductScraper class to EXAMPLES.md and performance tips to ADVANCED.md
Add error recovery patterns: what to do when selectors return None, how to handle changed page structures, retry logic examples
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary framing ('You are an expert...', 'Core Expertise' list) and the 'Key Principles' section states things Claude already knows (PEP 8, error handling). However, the code examples themselves are lean and efficient. | 2 / 3 |
Actionability | Excellent executable code throughout - all examples are copy-paste ready with proper imports, complete function definitions, and a full working ProductScraper class. No pseudocode; everything is concrete and runnable. | 3 / 3 |
Workflow Clarity | The skill presents patterns and examples clearly but lacks explicit validation checkpoints. For scraping workflows that can fail (network errors, changed HTML structure), there's no feedback loop for error recovery or validation steps to verify extracted data quality. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear section headers, but it's a monolithic document (~300 lines) that could benefit from splitting advanced topics (performance optimization, complete scraper class) into separate reference files. No external file references are provided. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 13 / 16 Passed | |
- Repository
- mindrally/skills
- Commit
47f47c1
- 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.