CtrlK
BlogDocsLog inGet started
Tessl Logo

cognition

Produce emotion.json and intention.json from workspace context.

56

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./agentsociety/packages/agentsociety2/agentsociety2/agent/skills/cognition/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 highly actionable with concrete schemas, formulas, and a worked example, and is well-structured with real bundle references. Minor tightening of repeated tables and a clearer validation retry loop would push it higher.

DimensionReasoningScore

Conciseness

The body is dense and largely token-efficient, skipping basic-concept padding, though a few tables and layer explanations could be trimmed, fitting anchor 4.

4 / 5

Actionability

Provides copy-paste-ready JSON schemas, an executable script command, a concrete TPB computation formula, modifier tables, and a worked example calculation, matching the fully-executable anchor 5.

5 / 5

Workflow Clarity

An explicit 7-step Execution Sequence plus a Validation Checklist and continuity rules give clear sequencing with most checkpoints present, fitting anchor 4; no destructive/batch cap applies to non-destructive state writes.

4 / 5

Progressive Disclosure

Real one-level-deep references to references/research_basis.md and scripts/update_cognition.py (both present) are clearly signaled, with good section structure and only minor inline bulk, fitting anchor 4.

4 / 5

Total

17

/

20

Passed

Description

46%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 clear about what it produces but omits any trigger guidance, which caps completeness and leaves trigger-term quality weak. It is reasonably distinct as a niche but would benefit from a "Use when..." clause.

Suggestions

Add a 'Use when...' clause with natural trigger phrases (e.g., 'Use when appraising the agent's emotional state or selecting a goal/intention each tick').

Include user-facing synonyms like 'emotion', 'mood', 'intention', 'goal', or 'affective state' rather than only file-name jargon.

Name a couple of concrete actions (e.g., 'appraise Scherer-style emotion checks and score TPB intentions') to lift specificity above generic 'produce'.

DimensionReasoningScore

Specificity

Names the domain and two concrete outputs ("Produce emotion.json and intention.json") but the actions are generic ("from workspace context") and not comprehensive, matching anchor 3.

3 / 5

Completeness

A clear "what" is stated but no "when"/trigger clause exists, so per the missing-Use-when cap it lands at anchor 3.

3 / 5

Trigger Term Quality

Only technical file-name jargon ("emotion.json", "intention.json", "workspace context") appears; there are no natural trigger phrases a user would say, sitting just above pure jargon at anchor 2.

2 / 5

Distinctiveness Conflict Risk

The emotion/intention cognition niche is mostly distinct with only minor overlap risk against other state skills, fitting anchor 4.

4 / 5

Total

12

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

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.