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

80%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/add-emacs/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-3

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 strong validation checkpoints and concrete commands for three Emacs distributions. Weaknesses are mild verbosity in the intro/feature prose and a broken external reference to a missing REMOVE.md.

Suggestions

Provide the referenced REMOVE.md (or inline the removal steps) so the "See [REMOVE.md](REMOVE.md)" link resolves, raising progressive_disclosure.

Trim the "What you can do with this" list and deduplicate the Channel Info vs Features sections to improve conciseness.

Consider moving the Troubleshooting section into a reference file to keep SKILL.md a leaner overview once the bundle is present.

DimensionReasoningScore

Conciseness

Mostly efficient and project-specific (install, env, wiring, troubleshooting Claude would not already know), but the "What you can do with this" bullet list and the overlap between Channel Info and Features prose could be tightened, so it is not fully lean.

2 / 3

Actionability

Provides fully executable, copy-paste-ready guidance — git fetch/show commands, file paths, env-var block, three distribution-specific elisp snippets, and curl/SQL verification commands — with only clearly user-specific placeholders.

3 / 3

Workflow Clarity

Sequences Pre-flight → Fetch → Copy → Append import → Build and validate with an explicit "Both must be clean before proceeding" checkpoint, idempotency guards, and a described integration-test feedback loop.

3 / 3

Progressive Disclosure

Sections are well-organized and the single reference is clearly signaled, but "See [REMOVE.md](REMOVE.md)" points to a file that is absent from the bundle, and the ~300-line body is somewhat monolithic.

2 / 3

Total

10

/

12

Passed

Description

82%Weight 40%Scale 1-3

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, distinctive description that names concrete capabilities and natural trigger terms. Its main gap is the absence of an explicit "Use when..." trigger clause, which caps completeness at 2.

Suggestions

Append an explicit trigger clause such as "Use when the user wants to add Emacs as a NanoClaw channel, talk to the assistant from within Emacs, or send org-mode subtrees for review." to raise completeness to 3.

Consider adding a common user phrasing (e.g. "Emacs integration") to broaden the natural trigger term coverage slightly.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Add Emacs as a channel", "Opens an interactive chat buffer and org-mode integration", "Local HTTP bridge" — rather than vague language, matching the multiple-specific-actions anchor.

3 / 3

Completeness

Clearly answers what it does, but lacks any explicit "Use when..." trigger clause, so per the judging guidelines completeness is capped at 2 rather than 3.

2 / 3

Trigger Term Quality

Covers natural terms a user would say — "Emacs", "chat buffer", "org-mode", "Doom, Spacemacs, or vanilla", "NanoClaw" — giving good coverage of the keywords for this request.

3 / 3

Distinctiveness Conflict Risk

Scoped specifically to Emacs as a NanoClaw channel with distribution names, making it clearly distinguishable and unlikely to trigger for unrelated skills.

3 / 3

Total

11

/

12

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.