Token导航 LogoToken导航

Agent Skill · 开发

nlp-pipeline-builder(NLP 管道构建器)

nlp-pipeline-builder 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

nlp-pipeline-builder 是开发类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在开发类的 21,746 个 Skill 里排第 4,524。

总安装 8,071周安装 370GitHub Stars 3下载 2,764核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:nlp-pipeline-builder(NLP 管道构建器)
来源仓库:https://github.com/jmsktm/claude-settings
仓库路径:skills/nlp-pipeline-builder
安装命令:
npx skills add https://github.com/jmsktm/claude-settings --skill 'NLP Pipeline Builder'
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/jmsktm/claude-settings --skill 'NLP Pipeline Builder'

这个 Skill 是做什么的

开发类 Skill 面向写代码、改代码和排查问题,一般会读写仓库文件,部分还会执行构建或测试命令。

nlp-pipeline-builder 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息。适合在 Codex、Claude、Cursor、Gemini CLI 中围绕仓库状态、代码变更或协作事项进行整理。

通过 npx skills add 命令从指定 GitHub 仓库安装,需结合原始 README 核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/nlp-pipeline-builder

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/jmsktm/claude-settings --skill 'NLP Pipeline B…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

nlp-pipeline-builder 怎么安装?

在终端执行 npx skills add https://github.com/jmsktm/claude-settings --skill 'NLP Pipeline Builder'。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

nlp-pipeline-builder 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

nlp-pipeline-builder 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

nlp-pipeline-builder 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

nlp-pipeline-builder 用的人多吗?

公开数据是累计安装 8,071 次,近一周安装 370 次,下载 2,764 次,GitHub 3 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

nlp-pipeline-builder 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理开发类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

开发类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
skill-vetter

技能审查员 · OpenClaw

8,779,018986操作浏览器MIT-0通过
ontology

本体论 · OpenClaw

6,636,960576只读MIT-0通过
entra-app-registration

内部应用程序注册 · Codex、Claude

6,631,872764接触敏感数据未明确通过
entra-app-registration

内部应用程序注册 · Codex、Claude

3,757,680201接触敏感数据未明确通过
nano-banana-pro

纳米香蕉专业版 · OpenClaw

3,526,898364接触敏感数据MIT-0有提醒
nlp-pipeline-builder

NLP 管道构建器 · 本页

8,0713只读未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

NLP Pipeline Builder

The NLP Pipeline Builder skill guides you through designing and implementing natural language processing pipelines that transform raw text into structured, actionable insights. From preprocessing to advanced analysis, this skill covers the full spectrum of NLP tasks and helps you choose the right approach for your specific needs.

Modern NLP offers multiple paradigms: rule-based approaches, classical ML, and deep learning/LLMs. This skill helps you navigate these options, building pipelines that balance accuracy, latency, cost, and maintainability. Whether you need real-time processing at scale or deep analysis of specific documents, this skill ensures your pipeline is fit for purpose.

From tokenization to semantic analysis, from single documents to streaming text, this skill helps you build robust NLP systems that handle real-world text with all its messiness and complexity.

Core Workflows

Workflow 1: Design NLP Pipeline Architecture

  1. Define requirements:

- Input: What text? What format? What volume? - Output: What information to extract? - Constraints: Latency, accuracy, cost

  1. Select pipeline stages: Standard NLP Pipeline: Text → Preprocessing → Tokenization → Feature Extraction → Task Model → Output Example stages: - Preprocessing: cleaning, normalization - Linguistic: tokenization, POS, NER, parsing - Semantic: embeddings, topic modeling - Task-specific: classification, extraction, generation
  2. Choose approach per stage: Stage Classical Deep Learning LLM Tokenization Regex, NLTK SentencePiece Model-specific NER CRF, rules BiLSTM-CRF, BERT Prompt-based Classification SVM, NB CNN, BERT Zero/few-shot Extraction Regex, patterns Seq2Seq Prompt-based
  3. Design error handling and fallbacks
  4. Document architecture

Workflow 2: Implement Text Preprocessing

  1. Clean text: def clean_text(text): # Normalize unicode text = unicodedata.normalize("NFKC", text) # Remove or replace problematic characters text = remove_control_characters(text) # Normalize whitespace text = " ".join(text.split()) # Optionally: lowercase, remove punctuation, etc. # (depends on downstream tasks) return text
  2. Segment into units:

- Sentence splitting - Paragraph detection - Document structuring

  1. Tokenize appropriately:

- Word tokenization for analysis - Subword tokenization for models - Language-specific considerations

  1. Normalize for consistency:

- Case normalization - Lemmatization/stemming - Handling contractions, abbreviations

Workflow 3: Build Production NLP System

  1. Set up processing infrastructure: class NLPPipeline: def __init__(self, config): self.preprocessor = TextPreprocessor(config) self.tokenizer = load_tokenizer(config.tokenizer) self.models = {"ner": load_model(config.ner_model), "sentiment": load_model(config.sentiment_model), "classification": load_model(config.classifier)} self.cache = ResultCache() if config.use_cache else None def process(self, text, tasks=None): tasks = tasks or ["all"] # Preprocessing cleaned = self.preprocessor.clean(text) tokens = self.tokenizer.tokenize(cleaned) # Run requested analyses results = {"text": text, "tokens": tokens} for task, model in self.models.items(): if task in tasks or "all" in tasks: results[task] = model.predict(tokens) return results
  2. Implement batching for throughput
  3. Add caching for repeated inputs
  4. Set up monitoring and logging
  5. Test with diverse inputs

Quick Reference

ActionCommand/Trigger
Design pipeline"Design NLP pipeline for [task]"
Preprocess text"How to preprocess [text type]"
Choose tokenizer"Best tokenizer for [use case]"
Extract entities"Extract entities from text"
Classify text"Build text classifier"
Scale pipeline"Scale NLP to [volume]"

Best Practices

  • Understand Your Text: Different text requires different treatment

- Social media: informal, abbreviations, emoji - Legal/medical: domain terms, structure - Multilingual: language detection, appropriate tools

  • Preserve What Matters: Preprocessing shouldn't destroy information

- Don't lowercase if case is meaningful - Keep punctuation if it affects meaning - Document all transformations

  • Handle Encoding Correctly: Unicode is tricky

- Always normalize (NFKC recommended) - Handle encoding errors gracefully - Test with diverse scripts and characters

  • Batch for Efficiency: Model inference is expensive

- Batch inputs for GPU utilization - Balance batch size vs latency - Use async processing where appropriate

  • Fail Gracefully: Text is messy and unpredictable

- Handle empty, too-long, or malformed inputs - Provide sensible defaults for edge cases - Log failures for analysis

  • Version Your Pipeline: Reproducibility matters

- Pin model versions - Document preprocessing steps - Track configuration changes

Advanced Techniques

Multi-Stage Extraction Pipeline

Chain extractors for complex information:

class ExtractionPipeline:
    def __init__(self):
        self.ner = NERModel()
        self.relation = RelationExtractor()
        self.coreference = CoreferenceResolver()

    def extract(self, text):
        # Stage 1: Named Entity Recognition
        entities = self.ner.extract(text)

        # Stage 2: Coreference Resolution
        resolved = self.coreference.resolve(text, entities)

        # Stage 3: Relation Extraction
        relations = self.relation.extract(text, resolved)

        # Stage 4: Build knowledge graph
        graph = build_graph(resolved, relations)

        return {
            "entities": resolved,
            "relations": relations,
            "graph": graph
        }

Hybrid Classical + LLM Pipeline

Use LLMs where they add value, classical where they don't:

class HybridPipeline:
    def process(self, text):
        # Fast classical preprocessing
        cleaned = classical_clean(text)
        sentences = classical_sentence_split(cleaned)

        # Classical NER (fast, predictable)
        entities = classical_ner(sentences)

        # LLM for complex tasks (slower, more capable)
        sentiment = llm_sentiment(text)  # Nuanced sentiment
        summary = llm_summarize(text)    # Abstractive summary

        return {
            "sentences": sentences,
            "entities": entities,  # Classical
            "sentiment": sentiment,  # LLM
            "summary": summary  # LLM
        }

Streaming Text Processing

Handle continuous text streams:

class StreamingNLP:
    def __init__(self, batch_size=32, timeout_ms=100):
        self.batch_size = batch_size
        self.timeout_ms = timeout_ms
        self.buffer = []
        self.last_process_time = time.time()

    async def add(self, text):
        self.buffer.append(text)

        # Process if batch full or timeout
        if len(self.buffer) >= self.batch_size:
            return await self.flush()
        elif (time.time() - self.last_process_time) * 1000 > self.timeout_ms:
            return await self.flush()

    async def flush(self):
        if not self.buffer:
            return []

        batch = self.buffer
        self.buffer = []
        self.last_process_time = time.time()

        # Batch process
        results = await self.pipeline.process_batch(batch)
        return results

Language Detection and Routing

Handle multilingual text:

class MultilingualPipeline:
    def __init__(self):
        self.detector = LanguageDetector()
        self.pipelines = {
            "en": EnglishPipeline(),
            "es": SpanishPipeline(),
            "zh": ChinesePipeline(),
            "default": UniversalPipeline()
        }

    def process(self, text):
        lang = self.detector.detect(text)
        pipeline = self.pipelines.get(lang, self.pipelines["default"])

        return {
            "language": lang,
            "results": pipeline.process(text)
        }

Common Pitfalls to Avoid

  • Over-preprocessing and destroying meaningful information
  • Ignoring Unicode normalization and encoding issues
  • Using word tokenizers for languages without spaces
  • Not handling edge cases (empty text, very long text)
  • Assuming English-only when users may send other languages
  • Running expensive models on every input when caching would help
  • Not batching model inference for throughput
  • Ignoring the latency impact of pipeline stages

平台分布

Codex

35.93%
按下载量换算993

Claude

28.46%
按下载量换算787

Cursor

19.23%
按下载量换算532

Gemini CLI

10.56%
按下载量换算292

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills