CtrlK
BlogDocsLog inGet started
Tessl Logo

occupational-health-analyzer

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

53

Quality

61%

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-claude/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

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

The body is a well-structured, actionable instruction-only skill with concrete scoring systems, screening guidance, and report templates. Its main weaknesses are conciseness (repetitive scoring tables and out-of-place version/date metadata) and progressive disclosure (everything inlined with no reference files despite the length).

Suggestions

Move the detailed scoring rubrics, occupational-disease screening tables, and the full report-format template into one-level-deep reference files (e.g., references/scoring.md, references/report-template.md) and link to them from SKILL.md to improve progressive disclosure.

Deduplicate the nearly identical 久坐 and 视屏终端 scoring tables (define the shared 0-10 dimension scale once) and relocate the version/last-updated metadata to a clearly marked metadata or changelog section to avoid the time-sensitive-info conciseness penalty.

Add explicit validate→fix→retry checkpoints after data reading and before report generation so the workflow's validation feedback loops are unambiguous.

DimensionReasoningScore

Conciseness

Mostly efficient domain-specific scoring data, but the久坐 and 视屏终端 scoring tables repeat near-identical structures, the output-format template is long, and a version (v1.0.0) plus date (2025-01-08) sit outside any deprecated/old-patterns section, which the rubric penalizes.

3 / 5

Actionability

Provides highly concrete, copy-paste-ready guidance — exact per-dimension point values, risk thresholds (4-40, 14-26, 27-40), ergonomic 0-100 scoring, screening items with frequencies, and a full report template — with only minor placeholder gaps.

4 / 5

Workflow Clarity

A clear six-step sequence (读取→评估→人机工程→筛查→关联→报告) with validation in step 1 (检查文件是否存在, 验证数据结构完整性) and a dedicated 错误处理 section for missing data, insufficient data, and high-risk warnings; minor checkpoint gaps keep it just below 5.

4 / 5

Progressive Disclosure

Well-organized into clear section headers, but with no bundle files present all content — detailed scoring rubrics, screening tables, and the full output template — is inlined in a ~380-line SKILL.md rather than split into one-level-deep reference files.

3 / 5

Total

14

/

20

Passed

Description

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

The description clearly states what the skill does in third person with several concrete actions, but omits any explicit 'when to use' trigger guidance, capping completeness and weakening trigger-term quality. Distinctiveness is reasonably strong thanks to the focused occupational-health domain.

Suggestions

Add an explicit 'Use when...' clause naming natural user triggers (e.g., 'Use when the user asks about work-related health risks, occupational health status, or workplace ergonomics') to raise completeness above 3.

Include natural synonyms and concrete trigger phrases users would actually say (e.g., 久坐风险, 办公室健康, 工位评估, 颈肩腰腿痛) rather than only formal domain terms.

Tighten the cross-module correlation mention so it signals collaboration with sibling skills without blurring the skill's distinct occupational-health trigger surface.

DimensionReasoningScore

Specificity

Lists several concrete third-person actions ('分析职业健康数据', '识别工作相关健康风险', '评估职业健康状况', '提供个性化职业健康建议') plus correlation analysis, with only minor coverage gaps; not quite the comprehensive multi-action level 5.

4 / 5

Completeness

The 'what' is clearly stated (analyze, identify risks, assess, advise, correlate), but there is no 'Use when...' clause or equivalent trigger guidance, so per the rubric completeness is capped at 3.

3 / 5

Trigger Term Quality

Contains relevant domain keywords (职业健康, 工作相关健康风险, 睡眠, 运动, 心理健康) but lacks natural user-facing variations, synonyms, or file/extension triggers users would actually say.

3 / 5

Distinctiveness Conflict Risk

The occupational-health niche is mostly distinct with its own triggers, though explicit correlation with sibling sleep/fitness/mental-health modules creates minor overlap risk with closely related skills.

4 / 5

Total

14

/

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.

Validation14 / 16 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

14

/

16

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.