Update to Nihontekini

{
  "description": "Use when a user asks how their Japanese learning is going, what is due, how many words they know, or for a weekly progress report.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 402
    }
  ],
  "name": "progress-check",
  "skill_md_contents": "---\nname: progress-check\ndescription: Use when a user asks how their Japanese learning is going, what is due, how many words they know, or for a weekly progress report.\n---\n\n## Workflow\n1. Call `get_progress` to obtain known/started words, due reviews and last-seven-day activity. Optionally call `get_weak_words` for concrete practice targets.\n2. Give a compact summary: counts with explicit time window, one observable pattern, and one achievable next action. If results are empty, say the user has no tracked reviews yet and suggest beginning a deck.\n3. Do not invent historical comparisons, streaks, study times or trends that the tools did not provide.\n\n## Cross-workflow rules\n- Use only Nihontekini MCP tools with exact server-returned IDs; never invent card, deck, quiz, or user IDs. Authentication failures: ask the user to reconnect the plugin.\n- Card `meaning` must contain only plain English glosses (e.g. `[\"to study\", \"diligence\"]`). Put kana in `reading`, usage and grammar in `explanation`, and never include romaji, pronunciation, kana, part of speech, or annotations inside `meaning`. The `reading` field contains kana, never romaji.\n- Examples should be natural, with Japanese text in `jp` and, when available, Anki-style furigana in example `reading`, e.g. `日本語[にほんご]を 勉強[べんきょう]しています。`.\n- In chat, when showing Japanese, give kana and romaji alongside kanji as appropriate; in a question that tests reading, never spoil the answer with reading or romaji.\n- Never include raw JSON tool payloads or credentials in the conversation. Summarize results concisely in the user's language.\n- Send at most 200 cards per add/suspend/delete request and 30 questions per quiz. On a 429 Too Many Requests, respect Retry-After and avoid hammering.\n- If a tool refuses (`isError`), pass its message on plainly and stop without retrying unless the message says what to change. Never claim the assistant can buy or change anything on the account.\n- Mention that newly created or edited cards appear on the phone after the next sync (pull to refresh). Never promise immediate propagation.\n"
}