CtrlK
BlogDocsLog inGet started
Tessl Logo

add-emacs

Add Emacs as a channel. Opens an interactive chat buffer and org-mode integration so you can talk to NanoClaw from within Emacs (Doom, Spacemacs, or vanilla). Local HTTP bridge — no bot token or external service needed.

65

Quality

79%

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 ./.claude/skills/add-emacs/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A highly actionable, well-sequenced install guide with explicit validation checkpoints and strong error-recovery guidance. The main improvement area is progressive disclosure: the single dense file could split troubleshooting or per-distribution config into referenced files.

DimensionReasoningScore

Conciseness

Mostly lean and instruction-dense with copy-paste commands and config blocks, though a few explanatory passages (the registration-test rationale, the agent-shared vs shared session explanation) could be trimmed without losing clarity.

4 / 5

Actionability

Fully executable guidance throughout: nc:copy/nc:append blocks, pnpm build/test commands, curl verification, and complete copy-paste elisp for Doom, Spacemacs, and vanilla covering the common cases.

5 / 5

Workflow Clarity

Clear numbered Install → Enable → Wire → Configure → Restart → Verify sequence with an explicit checkpoint ('Both must be clean before proceeding') and a Troubleshooting section providing error-recovery feedback loops; validation is present so no destructive-operation cap applies.

5 / 5

Progressive Disclosure

Well-organized with clear section headers and one clearly signaled reference (REMOVE.md), but the SKILL.md is a fairly dense single-file guide rather than an overview pointing to detailed materials, and no bundle files are present to split content into.

4 / 5

Total

18

/

20

Passed

Description

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

A specific, distinct description that names concrete capabilities and natural trigger terms, but it lacks an explicit 'Use when...' trigger clause, which caps its completeness. Adding trigger guidance would lift the weakest dimension.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user wants to chat with NanoClaw or send org-mode subtrees from inside Emacs (Doom, Spacemacs, or vanilla).'

Mention the headline use cases (code review of a region, meeting-note/action-item summarization, research capture) so the description's capability coverage matches the body.

Keep the third-person voice (currently correct) and avoid padding the existing concrete actions.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'Opens an interactive chat buffer and org-mode integration', 'talk to NanoClaw from within Emacs', 'Local HTTP bridge' — but omits capabilities the body details (code review, meeting notes, research capture), leaving minor coverage gaps.

4 / 5

Completeness

The 'what' is clear (adds an Emacs channel with chat buffer and org-mode integration over a local HTTP bridge), but there is no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Strong natural keywords users would say — 'Emacs', 'Doom', 'Spacemacs', 'vanilla', 'org-mode', 'NanoClaw' — covering the main distribution variants, though a few synonymous phrasings are absent.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear, narrow niche (Emacs channel for NanoClaw via local HTTP bridge) with distinct triggers (Emacs/Doom/Spacemacs/org-mode/NanoClaw) and minimal risk of matching an unrelated skill.

5 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository
nanocoai/nanoclaw
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.