CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

eve-chat-template-eve

Work safely on Eve-specific internals in the Eve chat template. Use when changing the Eve agent, withEve routes, eveChannel auth, useEveAgent, ClientSession/SessionState, persisted event logs, stream/resume behavior, connection authorization, Vercel Connect MCP connections, local Eve tools, or upstream Eve API assumptions.

Quality

92%

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

The canonical home for this skill is eve-chat-template-eve in vercel/eve

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 dense, well-organized set of project-specific invariants that respects the reader's intelligence and provides concrete symbols, paths, and commands throughout. Its weakest points are the absence of error-recovery loops in the verification workflow and the lack of executable examples for the most intricate flows (Skip synthesis, resume layering).

Suggestions

Add an explicit error-recovery loop to the Verification section (e.g., "if typecheck or build fails, fix and re-run before proceeding to the manual checks") to strengthen workflow feedback.

Include a minimal code sketch for the Skip flow — synthesizing the declined interaction.settled and cancelled turn.settled events — since it is the most intricate multi-step procedure and currently has no executable example.

DimensionReasoningScore

Conciseness

Nearly every bullet is a non-obvious project invariant Claude could not know (e.g., "Do not confuse chat_event.eventIndex with SessionState.streamIndex", "Buffering until newline is normal parsing, not app-level response buffering"), with no padding and no explanation of generic concepts. It assumes competence and every token earns its place.

5 / 5

Actionability

Guidance is consistently concrete: copy-pasteable commands (rg pattern, pnpm typecheck/build), exact file paths (agent/tools/<snake_case>.ts, app/_components/agent-chat.tsx), and code patterns (defineTool(...), connect(process.env.ENV_NAME ?? "local-name")). It falls short of fully executable because the trickiest flows — synthesizing declined interaction.settled/cancelled turn.settled on Skip, and layering resumed events — are described procedurally without any code sketch.

4 / 5

Workflow Clarity

There is a clear entry sequence ("First Pass": read AGENTS.md, then docs, then search) and explicit exit checkpoints ("Verification": pnpm typecheck, pnpm build before PR, plus a manual-flow checklist). Anchor 5 additionally requires error-recovery feedback loops ("if errors: fix and re-validate"), which are absent, so it fits anchor 4's "clear sequence with most checkpoints present".

4 / 5

Progressive Disclosure

No bundle files exist, and none are needed: the body is a compact ~30-bullet set of invariants organized under clear section headers, with one-level-deep, clearly signaled deferrals to real project docs (AGENTS.md, docs/how-the-chatbot-works.md, docs/setup-and-deploy.md, node_modules/eve/docs/). No dangling references to nonexistent bundle files.

5 / 5

Total

18

/

20

Passed

Description

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

This is a strong description: it states a clear purpose, provides an explicit and highly concrete "Use when" trigger list, and is unmistakably distinct from any other skill. The only minor weakness is that the capability side rests on a single generic verb ("Work safely on") rather than enumerated actions, which is reflected in the specificity score.

DimensionReasoningScore

Specificity

The only action verb is "Work safely on", but the enumerated surface ("withEve routes, eveChannel auth, useEveAgent, ClientSession/SessionState, persisted event logs, stream/resume behavior, Vercel Connect MCP connections") is highly specific with near-comprehensive coverage of the template internals. It sits above anchor 3 ("not comprehensive") because every named area is concrete, but below anchor 5, which requires multiple distinct concrete actions.

4 / 5

Completeness

It explicitly answers both questions: what ("Work safely on Eve-specific internals in the Eve chat template") and when ("Use when changing the Eve agent, withEve routes, ..." with a dozen concrete trigger phrases). Anchor 4's stated deficiency (a 'when' that could be more explicit) does not apply, and the explicit "Use when" clause avoids the completeness cap.

5 / 5

Trigger Term Quality

The description combines exact code identifiers ("useEveAgent", "ClientSession/SessionState", "withEve", "eveChannel") with natural phrases a user would say ("stream/resume behavior", "connection authorization", "persisted event logs", "local Eve tools"). Coverage is comprehensive for this domain, matching the anchor for full natural-term coverage rather than the "a few natural terms missing" anchor.

5 / 5

Distinctiveness Conflict Risk

Eve-specific identifiers (withEve, eveChannel, useEveAgent) carve out a clear niche that no generic skill would overlap with, giving minimal conflict risk. It matches the anchor for a clear niche with distinct triggers.

5 / 5

Total

19

/

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

thedotmack/claude-mem

Path

integrations/eve/template/.agents/skills/eve-chat-template-eve/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.