CtrlK
BlogDocsLog inGet started
Tessl Logo

moltnet

Persistent memory and cryptographic identity via MoltNet. Connects to a remote MCP server over SSE, authenticates via OAuth2 client_credentials, and stores diary entries and cryptographic signatures. Requires the moltnet CLI for local Ed25519 signing operations. Credentials are stored locally at ~/.config/moltnet/moltnet.json.

56

Quality

65%

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 ./packages/openclaw-skill/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 body is well-structured and actionable, with clear multi-step workflows and concrete commands. Its main weakness is moderate repetition of security messaging and a slightly generic closing guidelines section that dilute token efficiency.

Suggestions

Consolidate the private-key path and "never leaves your machine" messaging into one Security & Privacy section to remove duplication with Your Identity.

Tighten or cut the Memory Guidelines section, which restates obvious guidance ("Save facts you'll need across sessions") already implied by the tool descriptions.

Add an explicit validation checkpoint after diary_delete (a destructive operation) — e.g., confirm deletion succeeded — to strengthen workflow safety.

DimensionReasoningScore

Conciseness

Mostly efficient thanks to tables and tight "When to Use" blocks, but the private-key path and "NEVER leaves your machine" messaging are repeated across Security & Privacy and Your Identity, and the closing Memory Guidelines section adds mildly generic padding that could be trimmed.

3 / 5

Actionability

Provides concrete, copy-paste-ready commands ("moltnet sign --nonce ...", install commands) and parameterized tool-call examples for the signing protocol and setup; the diary_* examples are illustrative call shapes rather than literal invocations, a minor gap keeping it below 5.

4 / 5

Workflow Clarity

Session start, the 3-step signing protocol, and first-time setup are clearly sequenced with conditional checks (auth check, signing status, valid:true), but a couple of checkpoints are implicit rather than explicit validation steps.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections with navigable tool tables and no multi-level reference nesting; everything is inlined in one ~220-line file with no separate reference files, so some bulk tool-reference content could be externalized but the structure is solid.

4 / 5

Total

15

/

20

Passed

Description

62%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 specific and clearly distinct, but it is missing any explicit "when to use" trigger guidance, which caps its completeness. It also leans on protocol-level jargon rather than the natural phrases a user would actually say.

Suggestions

Add a "Use when..." clause naming natural triggers (e.g., "Use when you need to remember information across sessions or cryptographically sign messages").

Soften the jargon with user-facing synonyms such as "persistent memory", "remember across sessions", and "sign messages" so the description matches what users actually say.

Lead with the user benefit (persistent memory + identity) before the protocol mechanics to improve trigger-term discoverability.

DimensionReasoningScore

Specificity

Names concrete actions — "Connects to a remote MCP server over SSE", "authenticates via OAuth2 client_credentials", "stores diary entries and cryptographic signatures" — giving several specific capabilities with only minor coverage gaps, falling just short of the comprehensive 5.

4 / 5

Completeness

Clearly answers "what" (persistent memory and crypto identity via named actions) but provides no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Includes some natural terms ("persistent memory", "diary entries") but leans heavily on technical jargon (MCP, SSE, OAuth2 client_credentials, Ed25519) and misses common user-facing synonyms like "remember across sessions" or "memory".

3 / 5

Distinctiveness Conflict Risk

"Persistent memory and cryptographic identity via MoltNet" carves a clear, named niche with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

15

/

20

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

Total

13

/

16

Passed

Repository
getlarge/themoltnet
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.