CtrlK
BlogDocsLog inGet started
Tessl Logo

plan

Execute intentions through the environment.

41

Quality

40%

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

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.

The content is a well-structured, actionable guide with concrete schemas, clear multi-step workflows, and explicit error-handling checkpoints. Its main weakness is some conceptual padding around dual-process theory that could be trimmed for token efficiency.

Suggestions

Trim the System 1/System 2 psychological exposition to its operational triggers and outputs, dropping the explanatory prose Claude already knows.

Add one explicit worked example of composing a codegen instruction from an intention to close the actionability gap.

Consolidate the overlapping interrupt/adjustment sections (Need-Driven Plan Adjustment vs Plan Interruption) to reduce redundancy.

DimensionReasoningScore

Conciseness

The body is mostly compact with tight tables and JSON snippets, but the dual-process (System 1/2) and habit-formation framing spends tokens on conceptual psychology Claude already understands rather than purely operational guidance.

3 / 5

Actionability

Concrete JSON schemas for plan_state.json and codegen calls plus explicit file paths give mostly executable guidance, with only minor gaps around how the codegen instruction text is actually composed.

4 / 5

Workflow Clarity

Sequenced workflows (Multi-Step Plans, Resume Logic, Re-observation) include explicit validation checkpoints — checking codegen status, one-retry correction, and a 3-failure threshold — leaving only minor validation gaps.

4 / 5

Progressive Disclosure

The skill is a single well-sectioned file with no nested references and clear headers, organized for easy navigation; it is somewhat dense but appropriately self-contained.

4 / 5

Total

15

/

20

Passed

Description

13%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.

The description is too abstract and generic to function as an effective skill trigger: it states a vague capability without concrete actions, natural trigger terms, or any use-when guidance. It is largely indistinguishable from other action-execution skills.

Suggestions

Name concrete actions the skill performs (e.g., "Generate environment actions via codegen, maintain multi-step plan_state.json").

Add a "Use when..." clause with natural trigger phrases (e.g., "Use when you have an intention to act on the environment or need to plan multi-step goals").

Tighten distinctiveness by referencing the specific artifacts it manages (intention.json, plan_state.json) so it does not collide with other execution skills.

DimensionReasoningScore

Specificity

"Execute intentions through the environment" names a domain (intentions/environment) but the action is generic and minimal, matching the anchor for naming a domain with minimal actions.

2 / 5

Completeness

It offers only a vague "what" ("Execute intentions") and entirely omits any "when"/"Use when" guidance, matching the anchor for a vague what with no when.

2 / 5

Trigger Term Quality

No natural keywords a user would actually say; the phrasing is abstract technical language with no common trigger phrases, matching the lowest anchor.

1 / 5

Distinctiveness Conflict Risk

The phrasing is entirely generic and would overlap with virtually any action-oriented skill, matching the anchor for maximum conflict risk.

1 / 5

Total

6

/

20

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.

Validation — 16 / 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.