CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bls-query

Queries U.S. Bureau of Labor Statistics data using the BLS MCP server. Use when user asks about CPI, inflation, unemployment, employment, wages, jobs, labor statistics, producer prices, or any economic indicator tracked by BLS. Maps natural language to correct series IDs and tools. Copied from https://github.com/larasrinath/bls_mcp

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%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.

A well-structured, token-efficient workflow for an MCP-based skill: concrete IDs, a tool-selection table, explicit error recovery, and a real one-level-deep reference file. The only improvements are eliminating the duplicated fallback guidance between Steps 1 and 4 and adding a sample tool invocation.

DimensionReasoningScore

Conciseness

The body is lean — tables, short bullets, concrete IDs — with no explanation of concepts Claude already knows. Not a 5: Step 4 ('Handle unknowns') restates the identical get_all_surveys/get_popular_series fallback already given at the end of Step 1, which is trimmable redundancy.

4 / 5

Actionability

Concrete, executable guidance throughout: exact series IDs (CUUR0000SA0, LNS14000000), named MCP tools in a decision table, and a numbered fallback procedure. Not a 5: no example tool invocation showing argument format (e.g., series_id, start_year), leaving a minor gap in copy-paste readiness.

4 / 5

Workflow Clarity

A clear four-step sequence with an explicit ambiguity checkpoint in Step 1, a dedicated unknowns loop in Step 4, a 'Do NOT guess a series ID' guardrail, and error-recovery guidance in Common Issues (rate limits, empty results, ID not found). Not a 4: validation and feedback loops are explicit rather than implicit, satisfying the anchor-5 criteria.

5 / 5

Progressive Disclosure

The body is a concise overview holding only the most common mappings, with the full catalog clearly signaled in references/series-catalog.md (verified to exist and contain the series catalog), exactly one level deep. Content is appropriately split between inline quick mappings and the reference file.

5 / 5

Total

18

/

20

Passed

Description

82%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, concise description with an explicit 'Use when' trigger clause and excellent natural-language keyword coverage. Its only weaknesses are limited action enumeration (two verbs rather than several) and a provenance URL that consumes description budget without conveying capability.

Suggestions

Replace the 'Copied from <repo URL>' line with another concrete capability (e.g., 'retrieves latest values, historical trends, and multi-series comparisons') to raise specificity.

Add missing natural trigger terms such as 'job openings', 'JOLTS', 'nonfarm payrolls', and 'labor force participation' to round out trigger coverage.

DimensionReasoningScore

Specificity

"Queries U.S. Bureau of Labor Statistics data using the BLS MCP server" and "Maps natural language to correct series IDs and tools" name the domain and exactly two concrete actions. Not a 4: the anchor requires several specific actions, and the trailing "Copied from https://github.com/..." line adds no capability information.

3 / 5

Completeness

Explicitly answers both what ("Queries U.S. Bureau of Labor Statistics data... Maps natural language to correct series IDs and tools") and when ("Use when user asks about CPI, inflation, unemployment...") with concrete trigger phrases. Not a 4: the when-clause is fully explicit and specific, matching the anchor-5 example structure rather than the weaker 'when could be more explicit' anchor.

5 / 5

Trigger Term Quality

"CPI, inflation, unemployment, employment, wages, jobs, labor statistics, producer prices" are natural user phrasings with good synonym coverage. Not a 5: common variations like "job openings", "JOLTS", "payrolls", and "layoffs" are missing from the trigger list.

4 / 5

Distinctiveness Conflict Risk

Clear niche (U.S. Bureau of Labor Statistics via a specific MCP server) with distinct trigger terms like CPI, unemployment rate, and producer prices. Minimal overlap risk with any other skill category.

5 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

dathere/qsv

Path

.claude/skills/skills/bls-query/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.