CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

emergency-card

生成紧急情况下快速访问的医疗信息摘要卡片。当用户需要旅行、就诊准备、紧急情况或询问"紧急信息"、"医疗卡片"、"急救信息"时使用此技能。提取关键信息(过敏、用药、急症、植入物),支持多格式输出(JSON、文本、二维码),用于急救或快速就医。

Quality

76%

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/emergency-card/SKILL.md

The canonical home for this skill is emergency-card in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

56%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 lays out a clear six-step workflow with thorough data-source mapping and error handling, but it is a monolithic document relying on pseudocode and referencing files (a script and 'related documents') that are absent from the bundle. Splitting format specifications, examples, and extraction logic into real reference files would substantially improve it.

Suggestions

Add the actual scripts/generate_emergency_card.py (and any referenced example/test documents) to the bundle, or remove the CLI usage and '相关文档' pointers that currently reference non-existent files.

Move the format specifications (HTML/JSON/text/PDF/QR), example outputs, and test data into separate reference files and link them by name from SKILL.md, keeping only the workflow overview inline.

Replace the pseudocode JavaScript (undefined readFile/saveFile/generateQRCode helpers) with executable code, and add an output-validation checkpoint before the final confirmation step.

DimensionReasoningScore

Conciseness

The 430-line body is mostly domain-specific (data source paths, JSON schemas) but includes tightening opportunities: duplicated sections (two "#### 2.4", chronicConditions stored twice in the output object), "(新增)" edit annotations, and a ~45-line ASCII card mockup that could be condensed.

3 / 5

Actionability

Guidance is detailed but the JavaScript is pseudocode — readFile, glob, saveFile, generateQRCode, calculateAge are undefined helpers — and the documented CLI ("python scripts/generate_emergency_card.py") references a script that does not exist in the bundle.

3 / 5

Workflow Clarity

Steps 1–6 are clearly sequenced and a dedicated error-handling section covers missing data, read failures, and QR-code fallback, but there is no checkpoint validating the generated output before reporting success.

4 / 5

Progressive Disclosure

Section headers give reasonable structure, but everything is inlined in one long file with no bundle files; three sections ("示例输出", "测试数据", "格式说明") point to unnamed "相关文档" that do not exist, and the scripts/ reference is dangling.

3 / 5

Total

13

/

20

Passed

Description

87%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: it states concrete capabilities, includes an explicit 'use when' clause with natural trigger phrases, and defines a distinct niche. Gaps are minor — a few missing format mentions and synonym triggers.

DimensionReasoningScore

Specificity

Lists several concrete actions — "提取关键信息(过敏、用药、急症、植入物)" and "支持多格式输出(JSON、文本、二维码)" — but omits formats detailed in the body (HTML, PDF), leaving minor coverage gaps.

4 / 5

Completeness

Explicitly answers both what ("生成紧急情况下快速访问的医疗信息摘要卡片" with extraction and output formats) and when ("当用户需要旅行、就诊准备、紧急情况或询问…时使用此技能") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases a user would say ("紧急信息", "医疗卡片", "急救信息", 旅行, 就诊准备) plus context keywords, though common variations like "急救卡" or "过敏卡" are missing.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (emergency medical information card) with distinct trigger terms that are unlikely to fire for unrelated skills.

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

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 8 missing

Warning

Total

14

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills/skills/emergency-card/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.