nlp-engineer

Diagnose and fix NLP pipeline reliability issues across processing, embeddings, and ranking.

22|2|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/jshsakura/awesome-opencode-skills --skill nlp-engineer-jshsakura
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nlp-engineer
Source: https://github.com/jshsakura/awesome-opencode-skills/tree/main/skills/nlp-engineer
Command: npx skills add https://github.com/jshsakura/awesome-opencode-skills --skill nlp-engineer-jshsakura

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineers build robust NLP pipelines by focusing on text processing quality, embeddings, ranking, and language-model-adjacent components to reduce linguistic errors in production.

Core Features & Use Cases

  • Map the NLP path: input processing, preprocessing, representation/ranking/generation, and downstream usage.
  • Identify where quality breaks (tokenization, normalization, retrieval mismatch, ranking drift, or prompt/context issues) and implement small safe fixes.
  • Validation across representative cases: one success, one edge case, and one failure path.
  • Focus on multilingual, domain-specific language handling, latency, cost, and evaluation design.

Quick Start

Diagnose and fix NLP pipeline issues across tokenization, embeddings alignment, and prompting for multilingual data.

Frequently Asked Questions about nlp-engineer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix ranking drift in an NLP pipeline?

To fix ranking drift in an NLP pipeline, map the processing path to identify where representation quality breaks, then implement the smallest safe fix. Validate changes across representative success, edge, and failure cases to ensure robustness and document remaining risks.

What is the best way to handle multilingual text processing and tokenization errors?

Handling multilingual text processing requires diagnosing tokenization and normalization issues within the pipeline. Apply targeted fixes to alignment and representation layers, validating against edge cases to maintain robustness across diverse domain-specific languages.

How do I evaluate NLP pipeline robustness and reduce latency costs?

Evaluating NLP pipeline robustness involves validating representative cases and analyzing latency alongside cost. Focus on embedding alignment and ranking efficiency to implement minimal safe fixes that improve overall system reliability without excessive computational overhead.

Why does retrieval mismatch occur in text embeddings and how do I resolve it?

Retrieval mismatch in text embeddings occurs when input preprocessing and representation layers fail to align. Resolve this by mapping the NLP path to pinpoint tokenization or normalization breaks, then applying the smallest safe fix and validating representative cases.

Can I use this approach for domain-specific language generation tasks?

Yes, this approach applies to domain-specific language generation tasks by diagnosing and fixing NLP pipeline reliability issues across input processing, embeddings, and prompting. It emphasizes evaluating representative cases to ensure generation quality and reduce linguistic errors.