CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

analyze-context

Estimate total token usage and cost across conversation history, system prompts, and active rules. Use when the user asks how much context or how many tokens are in use, to audit context size, or to estimate session cost.

71

Quality

89%

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 body is a tight, actionable procedure: exact estimation constants, a verified helper script, and a worked example that pins down the output format. The only weakness is minor redundancy from restating the formula and re-walking steps in the example.

Suggestions

State the calculation formula once: keep it in 'Estimation Method' and drop the duplicate "Or manual calculation: Total Chars * 0.3" line under Tools.

Mention the script's stdin mode (e.g., `echo "text" | deno run scripts/count_tokens.ts`) since the full conversation text is usually too long to pass as an argument.

DimensionReasoningScore

Conciseness

The body is lean with no explanation of concepts Claude already knows, but the formula is stated twice ("Token Count = Character Count * Multiplier" and again "Or manual calculation: Total Chars * 0.3") and the worked example partially restates the procedure. Efficient with minor trimmable instances, so 4 rather than 5.

4 / 5

Actionability

Fully executable guidance: the real command "deno run scripts/count_tokens.ts \"TEXT_snippet\"" (the script exists and matches its documented interface), the exact multiplier 0.3, and a complete numeric worked example ("12,000 * 0.3 = 3,600 tokens") covering the common case. No gaps.

5 / 5

Workflow Clarity

A clear 5-step sequence (Conversation, System/Rules, Overhead, Total, Report) with a worked example reinforcing it. The task is read-only estimation, so no validation checkpoints are needed, and the simple-skill exception applies to this short, single-purpose skill.

5 / 5

Progressive Disclosure

The skill is under 50 lines, well-organized into Scope/Estimation Method/Procedure/Tools/Examples, and correctly offloads calculation logic to the one-level-deep scripts/count_tokens.ts, which exists and is referenced with an accurate path. Per the rubric's simple-skill guideline this earns a 5.

5 / 5

Total

19

/

20

Passed

Description

83%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 cleanly states what the skill does and when to invoke it, with natural trigger phrases and third-person voice. It is specific and distinctive, with only minor gaps (missing synonyms like "context window" and slight overlap risk with generic cost-estimation skills).

DimensionReasoningScore

Specificity

"Estimate total token usage and cost across conversation history, system prompts, and active rules" plus "audit context size" names several concrete actions with an enumerated scope. Not 3 (only 1-2 actions) and not 5 (coverage is good but not comprehensive, e.g. tool-definition overhead is absent).

4 / 5

Completeness

Explicitly answers both what ("Estimate total token usage and cost across conversation history, system prompts, and active rules") and when ("Use when the user asks how much context or how many tokens are in use, to audit context size, or to estimate session cost") with concrete trigger phrases, matching the anchor-5 pattern.

5 / 5

Trigger Term Quality

Natural phrases users would say are present: "how much context", "how many tokens", "in use", "audit context size", "estimate session cost". Clearly above anchor 3, but common synonyms like "context window" or "token count" are missing, so not 5.

4 / 5

Distinctiveness Conflict Risk

Token/context auditing is a clear niche, but "estimate session cost" creates minor overlap risk with general pricing or cost-estimation skills. Mostly distinct rather than fully minimal conflict risk, so 4 rather than 5.

4 / 5

Total

17

/

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

korchasa/flowai-plugins

Path

plugins/flowai-engineering/skills/analyze-context/SKILL.md

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.