CtrlK
BlogDocsLog inGet started
Tessl Logo

japanese-writing-drafter

Detect when the operator corrects the agent's Japanese phrasing mid-conversation (rewrites a sentence, calls out a style problem, says 'this wording is bad, say it like X instead') and draft a pending writing-rule proposal into ~/.claude/writing-lint/proposals.jsonl for later human review. This skill is the ONLY writer of proposals.jsonl — it never edits rules.jsonl and never sets status to anything but pending. Promotion to rules.jsonl only happens via the human-run scripts/writing-rule-approve.sh. Use when user mentions writing-rule proposal, 表現を直して, 文体を直して, その言い方はNG, writing lint 提案, 指摘をルール化して. Do NOT load for: approving or rejecting proposals (use scripts/writing-rule-approve.sh), listing pending proposals (use scripts/writing-rule-list.sh), or scanning text against the existing dictionary (the writinglint engine / PostToolUse hook does that).

79

Quality

100%

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 japanese-writing-drafter in Chachamaru127/claude-code-harness

SKILL.md
Quality
Evals
Security

Quality

Content

100%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 tightly written and highly actionable: a concrete seven-step workflow with an embedded, schema-validating Python script, explicit validation and early-exit checkpoints, and well-signaled one-level references. It assumes Claude's competence and avoids redundant explanation.

DimensionReasoningScore

Conciseness

Lean and efficient: no padding, no explaining regex/JSON/Python basics, and every section (contract, triggers, steps, references) earns its place; the embedded script is necessary and directly actionable.

5 / 5

Actionability

Provides a fully executable copy-paste Python script with real schema validation, env-var path resolution, and directory creation; only REPO_ROOT/PATTERN_HERE/GOOD_HERE/EVIDENCE_HERE are per-invocation inputs the skill must fill.

5 / 5

Workflow Clarity

Seven clearly sequenced steps include an early-exit guard (skip if 'before' is too vague) and an explicit schema-validation checkpoint before the append, satisfying the validation requirement for shared-file writes.

5 / 5

Progressive Disclosure

A compact single-purpose skill with no bundle files; content is organized into clearly labeled sections and the 関連 section points one level deep to real external paths (schemas, scripts, engine), making navigation trivial.

5 / 5

Total

20

/

20

Passed

Description

100%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 exemplary: it states a precise single purpose, concrete file outputs, comprehensive bilingual triggers, and explicit boundaries that distinguish it from related approval/listing/scanning tools. Both the 'what' and 'when' are answered concretely with minimal fluff.

DimensionReasoningScore

Specificity

Names the domain and multiple concrete actions — detecting operator corrections, drafting a pending proposal, appending to proposals.jsonl, and explicitly never editing rules.jsonl or setting non-pending status — giving comprehensive, specific coverage.

5 / 5

Completeness

Explicitly answers both 'what' (draft a pending writing-rule proposal into proposals.jsonl for later human review) and 'when' (Use when user mentions writing-rule proposal, 表現を直して, etc.) with concrete trigger phrases.

5 / 5

Trigger Term Quality

Lists comprehensive natural trigger phrases in both English and Japanese (表現を直して, 文体を直して, その言い方はNG, 指摘をルール化して) plus a clear 'Do NOT load for' negative list, covering synonyms and actual operator phrasing.

5 / 5

Distinctiveness Conflict Risk

Carves a clear niche as the ONLY writer of proposals.jsonl and explicitly excludes approving, listing, and scanning (delegated to other scripts), minimizing conflict with sibling skills.

5 / 5

Total

20

/

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

referenced_paths_exist

Referenced path issues: 5 missing

Warning

Total

15

/

16

Passed

Repository
Chachamaru127/claude-code-harness
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.