CtrlK
BlogDocsLog inGet started
Tessl Logo

occupational-health-analyzer

分析职业健康数据、识别工作相关健康风险、评估职业健康状况、提供个性化职业健康建议。支持与睡眠、运动、心理健康等其他健康数据的关联分析。

45

Quality

48%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/occupational-health-analyzer/SKILL.md

The canonical home for this skill is occupational-health-analyzer in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

38%Scale 1-5

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

This skill is a comprehensive but overly verbose specification that reads more like a product requirements document than an actionable skill for Claude. It provides useful scoring formulas and risk thresholds but lacks executable code, proper validation checkpoints, and appropriate content splitting. The content would benefit significantly from being condensed into a concise overview with detailed scoring tables and templates moved to separate reference files.

Suggestions

Move the detailed scoring rubrics (sedentary risk, VDT risk, ergonomic assessment) and the full report template into separate reference files (e.g., SCORING.md, REPORT_TEMPLATE.md) and reference them from the main skill.

Add executable code examples showing how to read and parse the JSON data files, calculate risk scores, and generate the report output.

Add validation checkpoints between steps, e.g., 'Verify data has minimum required fields before proceeding to risk assessment' and 'Confirm risk scores are within valid ranges before generating report'.

Trim explanatory content that Claude already knows (e.g., what sedentary risk means, what VDT stands for) and focus on the specific scoring logic and decision rules unique to this skill.

DimensionReasoningScore

Conciseness

The skill is heavily verbose at ~350+ lines, extensively listing scoring rubrics, screening recommendations, and report templates that could be summarized or placed in separate files. Much of the content (e.g., explaining what sedentary risk is, listing every screening type) is information Claude already knows or could infer.

2 / 5

Actionability

The skill provides detailed scoring formulas and risk thresholds which are concrete, but there is no executable code—only pseudocode-like scoring tables. It references JSON data files but never shows how to parse them or perform actual calculations. The report template is a markdown skeleton rather than executable guidance.

3 / 5

Workflow Clarity

Steps 1-6 provide a clear sequence, and there is basic error handling. However, there are no validation checkpoints between steps (e.g., no 'verify risk scores before proceeding to ergonomic assessment'), and the correlation analysis step (Step 5) is extremely vague with no concrete methodology. The workflow involves health data analysis which could benefit from data validation feedback loops.

3 / 5

Progressive Disclosure

All content is inlined in a single monolithic file with no bundle files. The detailed scoring rubrics, report templates, screening recommendations, and error handling could easily be split into separate reference files. The skill references data files but provides no supporting bundle files for structure or examples.

2 / 5

Total

10

/

20

Passed

Description

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

The description does a good job listing specific capabilities in the occupational health domain and mentions cross-domain correlation analysis, which adds distinctiveness. Its main weaknesses are the absence of an explicit 'Use when...' trigger clause and the lack of natural user-facing trigger terms or synonyms that would help Claude match this skill to user requests.

Suggestions

Add an explicit 'Use when...' clause, e.g., '当用户提到职业健康、工作压力、职业病风险、工作环境健康评估时使用'

Include more natural trigger terms and synonyms users might say, such as '工作压力' (work stress), '职业病' (occupational disease), '工作疲劳' (work fatigue), '职场健康' (workplace wellness), '久坐' (sedentary work)

DimensionReasoningScore

Specificity

Lists several specific actions: analyzing occupational health data, identifying work-related health risks, assessing occupational health status, providing personalized occupational health advice, and supporting correlation analysis with sleep, exercise, and mental health data. Minor gaps remain (e.g., what specific outputs or formats are produced).

4 / 5

Completeness

The 'what' is clearly described with multiple concrete actions. However, there is no explicit 'when' clause — no 'Use when...' or equivalent guidance telling Claude when to select this skill. Per rubric guidelines, missing 'Use when...' caps completeness at 3.

3 / 5

Trigger Term Quality

Contains relevant domain keywords like '职业健康' (occupational health), '工作相关健康风险' (work-related health risks), '睡眠' (sleep), '运动' (exercise), '心理健康' (mental health). However, it lacks natural user-facing trigger terms, synonyms, or a 'Use when...' clause that would help match user queries. Users might say things like 'workplace wellness', 'ergonomics', 'burnout', or 'work stress' which are absent.

3 / 5

Distinctiveness Conflict Risk

The focus on '职业健康' (occupational health) specifically distinguishes it from general health or wellness skills. The mention of work-related health risks and correlation with sleep/exercise/mental health data creates a fairly distinct niche, though there could be minor overlap with general health analysis or mental health skills.

4 / 5

Total

14

/

20

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.

Validation9 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

9

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.