local-tools

Access local system resources including Calendar on macOS and Windows. Use this skill when you need to manage user's schedule directly on their device.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./SKILLs/local-tools/SKILL.md

Quality

Content

77%

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

The body is highly actionable with executable commands, JSON schemas, and well-sequenced validation workflows, but it is verbose and redundant across several overlapping sections and keeps reference-grade detail inline rather than splitting it into one-level-deep files.

Suggestions

Consolidate the duplicated 'Best Practices', 'Common Patterns', and 'Known Behaviors' sections and trim conceptual explanations (JXA, COM, BSD date, ISO 8601) that Claude already knows.

Move the error-code table, troubleshooting, and technical-details material into a separate reference file (e.g. references/TROUBLESHOOTING.md) linked one level deep from SKILL.md.

Keep only the quick-start commands, output format, and core workflow guidance inline to reduce token cost while preserving actionability.

Dimension	Reasoning	Score
Conciseness	The body (~470 lines) explains concepts Claude already knows (JXA, BSD date, COM API, ISO 8601, interval-overlap semantics) and repeats guidance across 'Best Practices', 'Common Patterns', a second 'Best Practices' section, 'Known Behaviors', and 'Technical Details'; it is mostly useful but padded and could be tightened, matching level 2 rather than the lean level 3.	2 / 3
Actionability	Every operation has copy-paste-ready executable commands with explicit flags (e.g. 'bash "<skill-dir>/scripts/calendar.sh" create --title ... --start ... --end ...'), plus full JSON output schemas and an error-code table, matching the 'fully executable code/commands; copy-paste ready' anchor.	3 / 3
Workflow Clarity	Risky/destructive flows are sequenced with explicit checkpoints — 'Always Check Before Creating', 'Search Before Updating/Deleting' to obtain the event ID, and an error-handling feedback loop that parses JSON and retries — matching the clear-sequence-with-validation anchor rather than the checkpoint-missing level 2.	3 / 3
Progressive Disclosure	The referenced bundle scripts (scripts/calendar.sh, scripts/calendar.ps1) are real and correctly linked one level deep, but SKILL.md is a monolithic ~470-line wall that inlines error-code tables, known behaviors, troubleshooting, and technical details which could be split into separate reference files, fitting the 'content that should be separate is inline' anchor.	2 / 3
	Total	10 / 12 Passed

Description

67%

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 answers what and when with an explicit trigger and is reasonably specific, but it relies on generic framing ('local system resources') and omits concrete sub-actions and common trigger terms (events, meetings) that would sharpen it.

Suggestions

Replace 'Access local system resources' with concrete actions, e.g. 'View, create, update, delete, and search calendar events on macOS and Windows'.

Add natural trigger terms users would say, such as 'meetings', 'appointments', or 'events', alongside 'Calendar' and 'schedule'.

Tighten the generic opening so the skill is clearly distinct from a broad 'local tools' skill and less likely to trigger for unrelated system-resource requests.

Dimension	Reasoning	Score
Specificity	Quotes 'Access local system resources including Calendar' and 'manage user's schedule' name the domain and a high-level action, but the description does not enumerate concrete sub-actions (view/create/update/delete appear only in the body), matching the 'names domain and some actions, but not comprehensive' anchor rather than the multi-action level 3.	2 / 3
Completeness	It states both what it does ('Access local system resources including Calendar on macOS and Windows') and an explicit when ('Use this skill when you need to manage user's schedule directly on their device'), clearly answering what AND when with an explicit trigger, matching the level-3 anchor.	3 / 3
Trigger Term Quality	It includes 'Calendar', 'schedule', and 'on their device', but omits common natural variations users say such as 'events', 'meetings', or 'appointments', fitting the 'some relevant keywords but missing common variations' anchor instead of the broad-coverage level 3.	2 / 3
Distinctiveness Conflict Risk	The opening 'Access local system resources' is generic and could overlap with other local-tool skills, though 'Calendar' plus platform and schedule references narrow it; it is 'somewhat specific but could still overlap' rather than having a fully clear niche.	2 / 3
	Total	9 / 12 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: netease-youdao/LobsterAI
Path: SKILLs/local-tools/SKILL.md
Commit: 2921c1e

Reviewed: about 10 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.