SKILLEMALL.ai
GitHub ↗ RU Sign in

AC japanese-translation-and-tutor

Japanese-English translator and language tutor. Use when: (1) User shares Japanese text and wants translation (news articles, tweets, signs, menus, emails). (2) User asks "what does X mean" for Japanese words/phrases. (3) User wants to learn Japanese grammar, vocabulary, or cultural context. (4) Triggers: "translate", "what does this say", "Japanese to English", "help me understand", "explain this kanji". Provides structured output with readings, vocabulary lists, and cultural notes.

modbender/skill-library-mcp Agent Skills author: modbender MIT 1 file body ≈ 379 tokens Open the sourcegithub.com↗ analyzed 3 d ago

Japanese-English translator and language tutor.

As a process C 62/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, failures and branches

ProcedureWriting and documentstype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
A
97/100
safety, quality, tests
Safety 60%
100
Quality 40%
92
Run on models
none yet
Process rating
C
62/100
Has gaps
Inputs and preconditions w 11
0
Failures and branches w 10
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 0

    ✓ No critical or high findings

    Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 62/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 20When it triggers. No condition that starts the skill
    • 60Result and completion. Output format stated, no completion criterion
    • 100Tools and files. No external tools needed
    • 100Steps. 9 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 379 tokens
    • 100Running it twice. No mutating operations

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +4Description does not say when NOT to use the skill (false activations)
    • +1No license
    • +2Single-language instructions
    • +5Description quotes 6 example trigger phrases
    • +3Description length 488: enough signal without eating the budget
    • +4Structure: 7 headings
    • +3Step-by-step instructions: 9 items
    • +3Output format is stated explicitly
    • +4Has examples (3 code blocks)

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 92.