CtrlK
BlogDocsLog inGet started
Tessl Logo

plan

Execute intentions through the environment.

46

Quality

47%

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 ./agentsociety/packages/agentsociety2/agentsociety2/agent/skills/plan/SKILL.md
SKILL.md
Quality
Evals
Security

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 concrete schemas, thresholds, and feedback-looped workflows, making it strong on actionability and workflow clarity. Its main weaknesses are conceptual padding explaining theory Claude already knows and a monolithic structure with no progressive disclosure.

Suggestions

Trim or remove the Dual-Process and Habit Integration theory explanations, keeping only the decision-mode selection rules and habit thresholds that drive behavior.

Split extended reference material (e.g. full plan_state.json schemas, habit formation tables) into a referenced file so SKILL.md stays a lean overview, enabling a higher progressive_disclosure score.

Deduplicate the overlapping Need-Driven Plan Adjustment and Plan Interruption sections into a single interruption-handling flow.

DimensionReasoningScore

Conciseness

The body is mostly efficient and actionable, but the Dual-Process Decision Making and Habit Integration sections explain Kahneman-style theory Claude already knows, and the Need-Driven Adjustment / Plan Interruption sections overlap, so it could be tightened; not 3 because of this conceptual padding, not 1 because the bulk is structured, actionable reference rather than dominated by padding.

2 / 3

Actionability

Concrete, copy-pasteable JSON examples for plan_state.json (normal and interrupted states), the codegen call, and habit output, plus specific file paths and numeric thresholds (satiety < 0.2, max 6 steps, 3 consecutive failures) meet the "fully executable; specific examples" anchor.

3 / 3

Workflow Clarity

Numbered workflows (Multi-Step Plans, Resume Logic, Workflow, Re-observation) with explicit feedback loops (retry one clearly different correction, mark failed after 3 consecutive failures, verify resume_conditions) match the "clear sequence with explicit validation and error-recovery" anchor.

3 / 3

Progressive Disclosure

The skill is a well-sectioned but monolithic ~215-line file with no external references, and content that could be split (dual-process theory, habit integration) is inline; the under-50-line simple-skill exemption does not apply, so it stops at 2 rather than 3, while good internal organization keeps it above 1.

2 / 3

Total

10

/

12

Passed

Description

17%

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 is too abstract and generic to effectively distinguish or trigger the skill: it names a single vague action and omits any explicit "Use when..." guidance. It reads like internal jargon rather than a user-facing trigger description.

Suggestions

Replace "Execute intentions through the environment" with concrete capabilities, e.g. "Generates and executes single-step and multi-step environment actions via codegen, maintaining plan_state.json for complex goals."

Add an explicit trigger clause such as "Use when you have an intention to act on and need to choose between a single-step action or a multi-step plan."

Include natural user-facing terms (e.g. "act on a goal", "continue a plan", "handle an interruption") so the skill triggers on real phrasings rather than internal vocabulary.

DimensionReasoningScore

Specificity

The phrase "Execute intentions through the environment" is a single abstract statement with no concrete, named capabilities, matching the vague "Helps with documents" / "Processes data" tier rather than score 2 which requires naming a concrete domain and some specific actions.

1 / 3

Completeness

It states a (vague) what but entirely lacks any "Use when..." or equivalent trigger guidance, so per the rubric it is capped at 2; it is not 1 because a what is present, and not 3 because when is absent.

2 / 3

Trigger Term Quality

Terms like "intentions" and "environment" are internal model jargon that no user would naturally utter when asking for this skill, fitting the "no natural keywords; technical jargon or overly generic" anchor.

1 / 3

Distinctiveness Conflict Risk

"Execute intentions through the environment" is maximally generic and would overlap with virtually any action-oriented skill, matching the "very generic; would conflict with many skills" anchor.

1 / 3

Total

5

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
XiaoLuoLYG/GOD
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.