SageMaker Serving Image Selection
huggingface/skills
Chooses the right serving container and current image URI for deploying a Hugging Face model to a SageMaker endpoint, preferring Hugging Face images over generic ones.
Search all Japanese NLP resources (libraries, models, datasets, tutorials, dictionaries, Hugging Face).
$ npx skills add taishi-i/awesome-japanese-nlp-resources --skill search -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install taishi-i/awesome-japanese-nlp-resources search --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/taishi-i/awesome-japanese-nlp-resources.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/awesome-japanese-nlp-resources/skills/search .claude/skills/search && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "search" agent skill from https://github.com/taishi-i/awesome-japanese-nlp-resources/tree/main/plugins/awesome-japanese-nlp-resources/skills/search into .claude/skills/search/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "search", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/taishi-i/awesome-japanese-nlp-resources/tree/main/plugins/awesome-japanese-nlp-resources/skills/searchType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add taishi-i/awesome-japanese-nlp-resources --skill search -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install taishi-i/awesome-japanese-nlp-resources search --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/taishi-i/awesome-japanese-nlp-resources.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/awesome-japanese-nlp-resources/skills/search .agents/skills/search && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "search" agent skill from https://github.com/taishi-i/awesome-japanese-nlp-resources/tree/main/plugins/awesome-japanese-nlp-resources/skills/search into .agents/skills/search/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "search", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add taishi-i/awesome-japanese-nlp-resources --skill search -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install taishi-i/awesome-japanese-nlp-resources search --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/taishi-i/awesome-japanese-nlp-resources.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/awesome-japanese-nlp-resources/skills/search .cursor/skills/search && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "search" agent skill from https://github.com/taishi-i/awesome-japanese-nlp-resources/tree/main/plugins/awesome-japanese-nlp-resources/skills/search into .cursor/skills/search/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "search", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/taishi-i/awesome-japanese-nlp-resources.git --path plugins/awesome-japanese-nlp-resources/skills/search--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add taishi-i/awesome-japanese-nlp-resources --skill search -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install taishi-i/awesome-japanese-nlp-resources search --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/taishi-i/awesome-japanese-nlp-resources.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/awesome-japanese-nlp-resources/skills/search .gemini/skills/search && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "search" agent skill from https://github.com/taishi-i/awesome-japanese-nlp-resources/tree/main/plugins/awesome-japanese-nlp-resources/skills/search into .gemini/skills/search/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "search", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install taishi-i/awesome-japanese-nlp-resources searchInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add taishi-i/awesome-japanese-nlp-resources --skill search -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/taishi-i/awesome-japanese-nlp-resources.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/awesome-japanese-nlp-resources/skills/search .github/skills/search && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "search" agent skill from https://github.com/taishi-i/awesome-japanese-nlp-resources/tree/main/plugins/awesome-japanese-nlp-resources/skills/search into .github/skills/search/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "search", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add taishi-i/awesome-japanese-nlp-resources --skill search -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install taishi-i/awesome-japanese-nlp-resources search --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/taishi-i/awesome-japanese-nlp-resources.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/awesome-japanese-nlp-resources/skills/search .opencode/skills/search && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "search" agent skill from https://github.com/taishi-i/awesome-japanese-nlp-resources/tree/main/plugins/awesome-japanese-nlp-resources/skills/search into .opencode/skills/search/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "search", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
searchSearch all Japanese NLP resources (libraries, models, datasets, tutorials, dictionaries, Hugging Face).
Search is an agent skill from taishi-i/awesome-japanese-nlp-resources. Search all Japanese NLP resources (libraries, models, datasets, tutorials, dictionaries, Hugging Face). Accepts keywords or natural language questions in any language. Use whenever the user asks which Japanese NLP resource to use, or wants to find one: tokenizers / morphological analyzers, BERT or LLM models, embeddings, NER, text classification, datasets / corpora, dictionaries, tutorials, or Hugging Face models. Trigger phrases include '日本語の形態素解析ライブラリ', 'おすすめの日本語tokenizer', '日本語BERTモデル', '日本語の感情分析データセット'…
Its SKILL.md is about 4.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It sits in AI & LLM Engineering, covering Natural language processing, Embeddings and Model hubs and datasets. It works with Hugging Face. The repository describes itself as: A curated list of resources for Japanese natural language processing (NLP): Python libraries, LLMs, dictionaries, corpora, and datasets. Includes Claude Code and Codex skills to… The licence is CC0-1.0.
7 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 451770b. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
BashFrom allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
pythonFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Search loads about 4.3k tokens when it runs. Until then it costs about 148 tokens; SKILL.md has 1,447 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
allowed-tools: BashAutomated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from taishi-i/awesome-japanese-nlp-resources at commit 451770b, republished under its CC0-1.0 licence (© taishi-i). 1,447 words, ~4,301 tokens.
.claude/skills/search/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.Search the awesome-japanese-nlp-resources database for the user's query.
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:
/awesome-japanese-nlp-resources:search, appended at the end of this skill as ARGUMENTS: …. Codex: the user's message that invoked $awesome-japanese-nlp-resources:search, minus that $… mention. If the skill was picked automatically rather than invoked by name, use the user's request as the query.${CLAUDE_PLUGIN_ROOT}. Codex: the directory two levels above this SKILL.md (use its absolute path).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 lists) — don't shorten it, drop passes, or alter its scores and thresholds./awesome-japanese-nlp-resources:<skill> in Claude Code, $awesome-japanese-nlp-resources:<skill> in Codex.Results 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 and link https://github.com/taishi-i/awesome-japanese-nlp-resources instead of answering from memory or web search.
If the query is empty or blank, stop immediately and output (in Codex, write the commands with $ instead of /):
Usage: /awesome-japanese-nlp-resources:search <query>
Examples:
/awesome-japanese-nlp-resources:search morphological analysis
/awesome-japanese-nlp-resources:search BERT
/awesome-japanese-nlp-resources:search named entity recognition
/awesome-japanese-nlp-resources:search text classification dataset
/awesome-japanese-nlp-resources:search sentence embedding
Please pass the keyword(s) you want to search for as the argument.
---
使い方: /awesome-japanese-nlp-resources:search <query>
クエリ例:
/awesome-japanese-nlp-resources:search 形態素解析
/awesome-japanese-nlp-resources:search BERT
/awesome-japanese-nlp-resources:search 固有表現認識
/awesome-japanese-nlp-resources:search テキスト分類 データセット
/awesome-japanese-nlp-resources:search 文埋め込み
検索したいキーワードを引数に指定してください。Do not proceed to Step 1 if the query is empty.
The data descriptions are in English, so always convert the query intent to English keywords before searching.
Keyword rules — read before choosing keywords:
morpholog catches "morphology", "morphological", "morphological analyzer". Other examples: embed → embedding/embeddings, classif → classification/classifier, translat → translation/translate, generat → generation/generative, segment → segmentation/segmenter, recogni → recognition/recognizer, extract → extraction/extractor, retriev → retrieval/retrieve.| Domain (Japanese query hint) | Stem keywords | Tool names to add |
|---|---|---|
| 形態素解析 / morphological analysis | morpholog, segment | mecab, janome, sudachi, kytea, kuromoji, jumanpp, nagisa |
| 固有表現認識 / NER | named entit, NER, recogni | ginza, spacy, knp |
| 係り受け解析 / dependency parsing | depend, parse, syntax | cabocha, knp, ginza, spacy |
| 文章分類 / text classification | classif, sentiment, categor | bert, fasttext |
| 感情分析 / sentiment analysis | sentiment, emotion, opinion | oseti, wrime |
| 埋め込み / word vectors / embeddings | embed, vector, represent | word2vec, fasttext, bert, sbert |
| 事前学習モデル / pretrained model | pretrain, language model, bert, gpt | bert, gpt, llama, rinna, elyza, calm, swallow |
| テキスト生成 / text generation | generat, language model | gpt, llm, llama, rinna, elyza |
| 機械翻訳 / machine translation | translat, machine translation | opus, marian, fairseq |
| 音声認識 / speech recognition | speech, recogni, audio, asr | whisper, julius, espnet |
| 音声合成 / text-to-speech | speech, synthesis, tts | voicevox, espnet |
| 質問応答 / QA | question, answer, qa | bert, t5 |
| 要約 / summarization | summari, abstract | bart, t5, pegasus |
| 辞書・IME / dictionary | dict, lexicon, ime | mecab, sudachi, mozc |
| コーパス・データセット / corpus | corpus, dataset, annot | (rely on stems) |
| チュートリアル / learning | tutorial, introduc, learn | (rely on stems) |
| OCR / 光学文字認識 | ocr, optical character, recogni | manga-ocr, donut, tesseract |
| RAG / 検索拡張生成 | retriev, rag, embed | ruri, glucose, faiss |
| ファインチューニング / fine-tuning | fine-tun, finetun, lora, peft | lora, peft, qlora |
| ベンチマーク・評価 / benchmark | benchmark, evaluat, jglue | llm-jp-eval, jglue, nejumi |
ja_keywords list. Aliases and some descriptions (al, d_ja — see Step 3) are Japanese-only, so a literal Japanese substring catches entries an English-only translation would miss entirely — nicknames like ボイボ (VOICEVOX), めかぶ (mecab), or a Japanese technical term that never got glossed into the English description. Leave ja_keywords empty for English queries.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, from docs/multilingual.md. The scripts below load it automatically when it exists; its items have categories like Multilingual (Speech recognition).
Do not read the data file directly (no Read tool, cat, head, or similar) — it is about 660 KB and would flood the context. Instead, run the scoring in a single shell command using Python.
Each item in the JSON array has:
u: GitHub or Hugging Face URLn: repository/model named: English descriptiond_ja: Japanese description (GitHub-origin items only; match your ja_keywords against this)al: curated alternate names / kana nicknames, e.g. ["VOICEVOX", "ボイスボックス", "ボイボ"] (array of strings, only ~40 items have this — treat a hit here as strong as a name match)c: category (e.g. Python library, HuggingFace Model (Text Generation), Corpus, Tutorial, Multilingual (Speech recognition), ...)s: subcategory / semantic labels (array of strings)st: GitHub star count (GitHub items only; absent or 0 otherwise)ns: normalized star score 0–10 (log-scaled, GitHub items only)dl: Hugging Face download count (HF items only; absent or 0 otherwise)nd: normalized download score 0–10 (log-scaled, HF items only)sc: pre-computed quality score (higher = more popular/active)status: "ok" or "not_found" — items whose repo 404s (~8 of ~1200) are filtered out below; never recommend oneRun the following, substituting RESOURCES_PATH with the absolute path from Step 2, keywords with your English keywords and ja_keywords with your raw Japanese terms, both from Step 1 (ja_keywords may be []):
python3 << 'EOF'
import json, os
with open("RESOURCES_PATH") as f: # absolute path from Step 2
data = json.load(f)
multilingual_path = os.path.join(os.path.dirname("RESOURCES_PATH"), "multilingual_resources.json")
if os.path.exists(multilingual_path):
with open(multilingual_path) as f:
data += json.load(f)
keywords = ["keyword1", "keyword2", "keyword3"] # English stems, from Step 1
ja_keywords = [] # raw Japanese terms from Step 1 -- [] for English queries
results = []
for item in data:
if item.get("status") == "not_found":
continue # dead repo -- never recommend it
n = item.get("n", "").lower()
d = item.get("d", "").lower()
d_ja = item.get("d_ja") or ""
s = " ".join(item.get("s") or []).lower()
c = item.get("c", "").lower()
al = " ".join(item.get("al") or []).lower()
text_score = 0
for kw in keywords:
kw = kw.lower()
if n == kw: text_score += 20
elif kw in n: text_score += 10
if kw in d: text_score += 5
if kw in s: text_score += 3
if kw in c: text_score += 2
if kw in al: text_score += 10 # alias hit is name-equivalent
for kw in ja_keywords:
if kw in n: text_score += 10
if kw in d_ja: text_score += 5
if kw in al: text_score += 10
if text_score < 8:
continue
ns = item.get("ns") or 0
nd = item.get("nd") or 0
sc = item.get("sc") or 0
pop = (ns if ns else nd) * 2.5
qual = min(5, sc * 5 / 21)
combined = text_score + pop + qual
results.append((combined, text_score, item))
results.sort(key=lambda x: -x[0])
seen = {item['n'] for _, _, item in results}
# Supplemental pass: surface high-popularity items from matching categories
# that may have been missed because their descriptions are in Japanese.
# Keys are stems to match against user keywords; values are category prefixes
# (prefix match covers "HuggingFace Model (Text Generation)" etc.).
CATEGORY_KEYWORDS = {
"tutorial": "Tutorial", "introduc": "Tutorial", "learn": "Tutorial",
"morpholog": "Python library", "segment": "Python library",
"mecab": "Python library", "janome": "Python library", "sudachi": "Python library",
"spacy": "Python library", "ginza": "Python library",
"corpus": "Corpus", "dataset": "Corpus",
"bert": "HuggingFace Model", "gpt": "HuggingFace Model",
"llm": "HuggingFace Model", "llama": "HuggingFace Model",
"pretrain": "HuggingFace Model", "embed": "HuggingFace Model",
"model": "Pretrained model",
}
supplement_cats = set()
for kw in keywords:
for ck, cat in CATEGORY_KEYWORDS.items():
if ck in kw.lower():
supplement_cats.add(cat)
if supplement_cats:
def cat_match(c):
return any(c == cat or c.startswith(cat + " ") for cat in supplement_cats)
extras = [
item for item in data
if cat_match(item.get("c", ""))
and (item.get("st", 0) or item.get("dl", 0))
and item["n"] not in seen
and item.get("status") != "not_found"
]
extras.sort(key=lambda x: -max(x.get("ns") or 0, x.get("nd") or 0))
for item in extras[:5]:
ns = item.get("ns") or 0
nd = item.get("nd") or 0
sc = item.get("sc") or 0
# base 8 = category-match credit (same as the text_score threshold)
combined = 8 + max(ns, nd) * 2.5 + min(5, sc * 5 / 21)
results.append((combined, 0, item))
seen.add(item["n"])
results.sort(key=lambda x: -x[0])
for combined, text_score, item in results[:20]:
st = item.get("st", 0) or 0
dl = item.get("dl", 0) or 0
flag = " [supplemental]" if text_score == 0 else ""
print(f"score={combined:.1f} text={text_score} st={st} dl={dl}{flag}")
print(f" n={item['n']}")
print(f" u={item['u']}")
print(f" c={item['c']}")
print(f" s={item.get('s','')}")
if item.get('al'):
print(f" al={item['al']}")
print(f" d={item.get('d','')[:120]}")
if item.get('d_ja'):
print(f" d_ja={item['d_ja'][:120]}")
print()
EOFThis returns up to 20 candidates. Items marked [supplemental] were added by the category-based pass to recover high-star resources whose descriptions are in Japanese. In Step 4, evaluate supplemental items on semantic fit before including them in the final list.
You now have up to 20 candidates. Apply your semantic judgment to produce the final ordered list of up to 10 results.
Re-rank by evaluating each candidate on:
Tutorial, Research summaryPretrained model, HuggingFace ModelCorpus, HuggingFace DatasetPython library, language-specific libsMultilingual (...) items; otherwise prefer Japanese-specific resources when they fit equally well, and use Multilingual (...) items to fill gaps such as speech, OCR, language detection or search enginessc is significantly higher among otherwise-similar items, it usually reflects more recent activity; prefer those.Do not mechanically follow the combined score from Step 3 — use it as a starting point, then move items up or down based on the criteria above.
Language detection rule (apply before writing any output):
Apply the detected language to all headings and prose.
Present the final re-ranked results:
## Search results for "<query>"
*(Searched for: keyword1, keyword2, ...)*
Found N result(s).
### 1. [repository-name](url)
**Category:** category > subcategory
**Popularity:** ⭐ {st} stars (or 📥 {dl} downloads for HF)
Description text here.
### 2. ...If no results, suggest alternate keywords and link to: https://github.com/taishi-i/awesome-japanese-nlp-resources
After the search results list, append a guide table that helps the user pick the right resource for their specific situation.
Match the section heading and table language to the query language — translate the heading and column headers into the query language (e.g. Japanese query → Japanese heading and headers).
## Use-case Selection Guide
| Use case | Recommended | Popularity | Why |
|---|---|---|---|
| ... | [name](url) | ⭐N or 📥N | short reason |Rules:
⭐{st} for GitHub stars, 📥{dl} for HuggingFace downloads. If both are 0, omit.© taishi-i, CC0-1.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file in plugins/awesome-japanese-nlp-resources/skills/search of taishi-i/awesome-japanese-nlp-resources.
Open the folder on GitHubat commit 451770b
Search next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Search this skilltaishi-i/awesome-japanese-nlp-resources | 1k | — | ~4.3k | Automated safety check: Notes | CC0-1.0 | |
| SageMaker Serving Image Selectionhuggingface/skills | 11k | 1 repos | ~4.6k | Automated safety check: Pass | Apache-2.0 | |
| Esmfold2JimLiu/science-skills | 228 | 4 repos | ~2.5k | Automated safety check: Pass | Apache-2.0 | |
| Hugging Face TokenizersOrchestra-Research/AI-Research-SKILLs | 13k | 6 repos | ~3.4k | Automated safety check: Pass | MIT | |
| Sentence Transformers EmbeddingsOrchestra-Research/AI-Research-SKILLs | 13k | 2 repos | ~1.6k | Automated safety check: Pass | MIT | |
| Hugging Face Transformers Usagedavila7/claude-code-templates | 33k | 11 repos | ~1.2k | Automated safety check: Pass | MIT |
huggingface/skills
Chooses the right serving container and current image URI for deploying a Hugging Face model to a SageMaker endpoint, preferring Hugging Face images over generic ones.
JimLiu/science-skills
Biohub ESMFold2 / ESMFold2-Fast all-atom co-folding (Candido et al.
Orchestra-Research/AI-Research-SKILLs
Shows how to load, train and use fast Hugging Face tokenizers, with BPE, WordPiece and Unigram models, padding, truncation and alignment tracking.
Orchestra-Research/AI-Research-SKILLs
Generates text embeddings locally with the sentence-transformers library for RAG, semantic search, clustering and similarity, with model picks for general, multilingual and legal text.
davila7/claude-code-templates
Loads pre-trained Hugging Face Transformers models for text, vision and audio tasks, runs inference with pipelines and fine-tunes on custom datasets.
wentorai/research-plugins
Run NLP and CV model inference via Hugging Face free-tier API
taishi-i/awesome-japanese-nlp-resources
Compare several Japanese NLP libraries, models, or datasets for a keyword (a specific tool name, or a function/task like '形態素解析') across a handful of criteria chosen for that comparison, rendered as…
taishi-i/awesome-japanese-nlp-resources
Analyze current trends and challenges in Japanese NLP for a topic.
taishi-i/awesome-japanese-nlp-resources
Given a Japanese NLP GitHub repo/model/dataset (URL / owner/repo / tool name) OR a topic, find what's already in awesome-japanese-nlp-resources and discover related resources NOT yet listed…
Works with
Categories
Search all Japanese NLP resources (libraries, models, datasets, tutorials, dictionaries, Hugging Face). Search is an agent skill from taishi-i/awesome-japanese-nlp-resources. Search all Japanese NLP resources (libraries, models, datasets, tutorials, dictionaries, Hugging Face).
Search fits situations like: the user asks which Japanese NLP resource to use; wants to find one: tokenizers / morphological analyzers; text classification; datasets / corpora.
Run `npx skills add taishi-i/awesome-japanese-nlp-resources --skill search -a claude-code`. Or copy the skill folder (plugins/awesome-japanese-nlp-resources/skills/search in taishi-i/awesome-japanese-nlp-resources) into .claude/skills/search in your project. Claude Code loads it when a task matches its description.
Run `npx skills add taishi-i/awesome-japanese-nlp-resources --skill search -a codex`. Or copy the skill folder (plugins/awesome-japanese-nlp-resources/skills/search in taishi-i/awesome-japanese-nlp-resources) into .agents/skills/search in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add taishi-i/awesome-japanese-nlp-resources --skill search -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/search, .gemini/skills/search, .github/skills/search and .opencode/skills/search in your project.
Going by SKILL.md and its folder, Search needs the command-line tools its instructions call (python). Our summary lists: Python 3. Its frontmatter pre-approves these tools: Bash.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
Search is published under the CC0-1.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 4.3k tokens (SKILL.md is roughly 17k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Search: SageMaker Serving Image Selection (huggingface/skills, 11k stars), Esmfold2 (JimLiu/science-skills, 228 stars), Hugging Face Tokenizers (Orchestra-Research/AI-Research-SKILLs, 13k stars) and Sentence Transformers Embeddings (Orchestra-Research/AI-Research-SKILLs, 13k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
taishi-i (a GitHub user) maintains it in taishi-i/awesome-japanese-nlp-resources, which has 1,021 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 6, 2026.
Source: taishi-i/awesome-japanese-nlp-resources on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.