mcp-tools-skill

Define and implement MCP tools for task CRUD operations

Install with Tessl CLI

npx tessl i github:WajahatAli3218664/Hackathon-02-mytodo --skill mcp-tools-skill

What are skills?

Review — 48%

Does it follow best practices?

If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:

npx tessl skill review --optimize ./path/to/skill

Learn more

Validation — 9 / 11 Passed

Validation for skill structure

SKILL.md

Review

Evals

Discovery

32%

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 provides a basic understanding of the skill's domain (MCP tools for task operations) but lacks the detail needed for effective skill selection. It's missing explicit trigger guidance, natural user keywords, and specific action examples that would help Claude confidently choose this skill over alternatives.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about creating MCP tool definitions, implementing task management APIs, or building CRUD endpoints for tasks'

Include natural keywords users might say: 'task management', 'to-do list API', 'create/read/update/delete tasks', 'task endpoints'

Expand specific capabilities: 'Define MCP tool schemas, implement create/read/update/delete handlers for tasks, validate task inputs, handle task persistence'

Dimension	Reasoning	Score
Specificity	Names the domain (MCP tools) and a general action (task CRUD operations), but doesn't list specific concrete actions like 'create tasks', 'update task status', 'delete completed tasks', or 'list tasks by project'.	2 / 3
Completeness	Only addresses 'what' at a high level. Completely missing a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes 'MCP tools' and 'CRUD operations' which are relevant but technical. Missing natural user terms like 'task management', 'to-do', 'create task', 'task list', or 'task API'.	2 / 3
Distinctiveness Conflict Risk	'MCP tools' provides some specificity, but 'task CRUD operations' is fairly generic and could overlap with other task management or API-related skills. The combination is somewhat distinctive but not clearly delineated.	2 / 3
	Total	7 / 12 Passed

Implementation

64%

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

This skill provides comprehensive, executable MCP tool implementations for task CRUD operations with good code quality and clear structure. However, it's verbose for a skill file, lacks explicit validation/error recovery workflows for database operations, and would benefit from better progressive disclosure by splitting detailed examples into separate files.

Suggestions

Add explicit validation workflow for bulk operations (e.g., 'Verify task IDs exist before bulk update, handle partial failures, provide rollback guidance')

Split the extensive code examples into a separate EXAMPLES.md or REFERENCE.md file, keeping SKILL.md as a concise overview with links

Remove the introductory paragraph and reduce repeated patterns (e.g., create a helper function for the common async session + user context pattern)

Add error handling guidance section covering common failure modes (database connection issues, permission errors, validation failures)

Dimension	Reasoning	Score
Conciseness	The skill is fairly efficient but includes some unnecessary verbosity like the introductory paragraph and could be tightened. The code examples are comprehensive but some patterns are repeated (e.g., the async with AsyncSessionLocal pattern appears many times).	2 / 3
Actionability	Provides fully executable Python code with complete implementations for all CRUD operations, Pydantic models, tool registration, and server setup. Code is copy-paste ready with proper imports and type hints.	3 / 3
Workflow Clarity	The project structure and code organization are clear, but there's no explicit validation workflow or error recovery guidance. For database operations and bulk updates, missing validation checkpoints (e.g., verify task exists before update, rollback on failure) cap this at 2.	2 / 3
Progressive Disclosure	Content is reasonably organized with sections for server setup, CRUD tools, and examples, but it's a monolithic file with ~350 lines of code that could benefit from splitting into separate reference files (e.g., SCHEMAS.md, EXAMPLES.md). No clear navigation to external resources.	2 / 3
	Total	9 / 12 Passed

Validation

81%

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 — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (569 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	9 / 11 Passed

Reviewed: 9 days 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.