toml

Create and review TOML configuration with strict typing and predictable structure. Use when editing tool configuration files that require schema-safe TOML.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./Skills/agent-ops/toml/SKILL.md

Quality

Content

67%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, lean instruction-only skill body with a clear procedure and validation checkpoint. Its main weakness is actionability: the validation guidance stays generic instead of naming concrete parsers or commands.

Suggestions

Replace 'Run the relevant parser/schema/tool checks' with concrete examples (e.g., `tomlq '.' file.toml`, `python -c 'import tomllib; tomllib.load(...)'`, or the owning tool's `--check` flag).

Make the validation feedback loop explicit: 'fix the reported blocker, then re-run validation until it passes' instead of only 'stop and report'.

Either link the remaining bundle files from the body or note that evals.yaml/contract.yaml/task-profile.json are eval/meta artifacts not part of skill guidance.

Dimension	Reasoning	Score
Conciseness	Lean bullet-style sections that assume Claude knows TOML without padding, though the redundant Table of Contents and several single-bullet sections (Philosophy, Gotchas) could be consolidated.	4 / 5
Actionability	Editing rules are concrete ('Change only the smallest required key path', 'Keep trailing commas out of arrays') but the central validation step is vague ('Run the relevant parser/schema/tool checks') with no specific command or parser named.	3 / 5
Workflow Clarity	A clear three-step Procedure with validation as the final checkpoint and a fail-fast rule, though the feedback loop halts ('stop and report') rather than explicitly fixing and re-validating.	4 / 5
Progressive Disclosure	Well-organized sections with a clearly signaled one-level reference to references/deep-guidance.md, but three of four bundle files (contract.yaml, evals.yaml, task-profile.json) are not referenced from the body.	4 / 5
	Total	15 / 20 Passed

Description

78%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 concise, well-formed description that clearly answers both what the skill does and when to use it, with natural trigger terms. It is slightly limited by naming only two actions and using a somewhat broad config-trigger phrase.

Suggestions

Add one or two more concrete actions (e.g., 'validate', 'migrate') to lift specificity from two verbs to several.

Include the '.toml' file extension and the 'config' synonym in the trigger clause for fuller keyword coverage.

Tighten the 'when' clause to name TOML-specific triggers (e.g., 'Use when editing .toml tool configs') to reduce overlap with general config skills.

Dimension	Reasoning	Score
Specificity	Names the TOML domain with two concrete actions ('Create and review TOML configuration') but offers only two verbs, falling short of the 'several specific actions' needed for a 4.	3 / 5
Completeness	Explicitly states both what ('Create and review TOML configuration with strict typing and predictable structure') and when ('Use when editing tool configuration files that require schema-safe TOML') with a concrete trigger phrase.	5 / 5
Trigger Term Quality	Includes natural terms users would say ('TOML configuration', 'tool configuration files', 'schema-safe TOML') with good coverage, though it omits the '.toml' extension and the 'config' synonym.	4 / 5
Distinctiveness Conflict Risk	TOML is a clear niche, but the broad 'tool configuration files' trigger carries minor overlap risk with related config skills such as the referenced YAML skill.	4 / 5
	Total	16 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: jscraik/Agent-Skills
Path: Skills/agent-ops/toml/SKILL.md
Commit: a3808a9

Reviewed: ~4 hours ago

Table of Contents

Discovery Implementation Validation

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.