/research

name: research
description: "Analyze current trends and challenges in Japanese NLP for a topic. Surveys the existing awesome-japanese-nlp-resources dataset and augments it with up-to-the-minute web research to produce a combined trend + issue report. Use only when the user explicitly wants a trend/landscape report, a challenges/limitations report, or a general research overview of a Japanese NLP topic (this combines the bundled dataset with live web research). Trigger phrases include '日本語LLMの最新トレンド', '〜の動向をまとめて', '最近の日本語NLPの流れ', '日本語LLMの課題', '〜の問題点・限界', '未解決の論点', 'trend report on Japanese embeddings', 'latest Japanese speech models', 'challenges in Japanese NER', 'limitations of Japanese embeddings'. For a simple lookup use the search skill; this one runs web research."
argument-hint: [topic]
allowed-tools: Bash WebSearch WebFetch

Research Japanese NLP trends and challenges for the user's topic by combining the bundled dataset with the latest web information.

Claude Code and Codex

This skill is shared by the Claude Code and Codex versions of the plugin. The steps are the same in both tools; only these details differ:

• **Topic** — Claude Code: the arguments of `/awesome-japanese-nlp-resources:research`, appended at the end of this skill as `ARGUMENTS: …`. Codex: the user's message that invoked `$awesome-japanese-nlp-resources:research`, minus that `$…` mention. If the skill was picked automatically rather than invoked by name, use the user's request as the topic.
• **Plugin root** — Claude Code: `${CLAUDE_PLUGIN_ROOT}`. Codex: the directory two levels above this `SKILL.md` (use its absolute path).
• **Shell** — run the commands below with Claude Code's `Bash` tool or Codex's shell tool. Copy each Python script in full and run it as written, changing only its placeholders (`RESOURCES_PATH`, the keyword list) — don't shorten it, drop passes, or alter its scores and thresholds.
• **Web** — Claude Code: `WebSearch` to search and `WebFetch` to read a page. Codex: the built-in web search tool (search, then open the page). Do not use the `gh` CLI, `curl`, or other network commands from the shell.
• **Commands** — write any command you show the user in the current tool's form: `/awesome-japanese-nlp-resources:<skill>` in Claude Code, `$awesome-japanese-nlp-resources:<skill>` in Codex.

Section 1 of the report ("What's already in awesome-japanese-nlp-resources") must come from the bundled data. If the data file can't be read (for example, shell commands are blocked or fail to start), say so in that section instead of filling it from memory or web search.

Instructions

Preamble — Establish the current date

Before anything else, run this once and remember the values — every step that mentions a year or the report date refers to them:

echo "YEAR_NOW=$(date +%Y)"
echo "YEAR_PREV=$(($(date +%Y) - 1))"
echo "REPORT_DATE_EN=$(LC_ALL=C date '+%B %-d, %Y')"
echo "REPORT_DATE_JP=$(date '+%Y年%-m月%-d日')"

Substitute these wherever this skill writes `${YEAR_NOW}`, `${YEAR_PREV}`, `${REPORT_DATE_EN}` or `${REPORT_DATE_JP}`. **Do not hardcode years.**

Step 0 — Validate input

If the topic is empty or blank, treat it as a request for a **general overview of the current Japanese NLP landscape** (both trends and challenges). Use the following defaults for the rest of the steps:

• **Topic label** for output headings: "Japanese NLP Overall Landscape" (use "日本語NLP 全体動向" only when the user's query was written in Japanese)
• **Keywords for Step 1** (local dataset survey): `llm`, `bert`, `embed`, `speech`, `morpholog`, `translat`, `evaluat`, `benchmark` — short stems, since Step 3 matches by literal substring and a multi-word phrase like `japanese nlp` rarely occurs verbatim in a description

— This broad set gives a cross-category snapshot of the most popular resources and of coverage gaps

• **Web searches for Step 5**: cover both trend and challenge language across multiple sub-fields:
• `japanese NLP trends ${YEAR_NOW} overview`
• `日本語 NLP 最新動向 ${YEAR_NOW}`
• `japanese LLM embedding benchmark ${YEAR_NOW} github`
• `japanese NLP challenges ${YEAR_NOW} overview`
• `日本語 NLP 課題 ${YEAR_NOW}`
• `japanese LLM limitations evaluation ${YEAR_NOW}`
• **Report title**: `## 🔭 Japanese NLP Research Report (as of ${REPORT_DATE_EN})` instead of `## 🔭 Research Report for "<topic>"` (use `## 🔭 日本語NLP リサーチレポート (${REPORT_DATE_JP}時点)` only when output language is Japanese)
• **Section 1 (Overview)**: write a broad 3–4 sentence overview covering the major active sub-fields (LLMs, embeddings/RAG, speech, morphological analysis, benchmarks) and the most pressing shared challenges

Step 1 — Interpret the topic

Translate the topic intent to English keywords for the local dataset survey. **Aim for 4–6 keywords**, using the same stem + tool-name conventions as the `search` skill (`morpholog`, `embed`, `classif`, `translat`, `recogni`, plus well-known tool names for the domain).

Step 2 — Locate the data file

The data file ships with the plugin at `data/resources.json` under the plugin root (see "Claude Code and Codex" above). Resolve its absolute path, falling back to a scoped search only if the install is unusual:

PLUGIN_ROOT="${CLAUDE_PLUGIN_ROOT}"  # Codex: replace with the plugin root, two levels above this SKILL.md
RESOURCES_PATH="$PLUGIN_ROOT/data/resources.json"
[ -f "$RESOURCES_PATH" ] || RESOURCES_PATH="$(find "${CODEX_HOME:-$HOME/.codex}/plugins" "${HOME}/.claude/plugins" -type f -name resources.json 2>/dev/null | grep "awesome-japanese-nlp-resources/" | head -1)"
echo "RESOURCES_PATH=$RESOURCES_PATH"

Use the resulting absolute `RESOURCES_PATH` wherever Step 3 opens the data file — write the path itself into the script, since shell variables may not persist between commands.

The plugin also ships `data/multilingual_resources.json` (same item format) listing multilingual libraries, models, and datasets (GitHub repositories) that also support Japanese, f