Skip to content
Back to skills

Pipeline Components

ASecurity

"Assemble and debug spaCy pipeline components, factories, registry

  • 247 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 9, 2026
databackend

Works with

  • cli

Security analysis

A100/100

Pro scans all 6 files and shows the line behind each finding

Scanned September 9, 2026

npx -y skills add VectorSpaceLab/AREX-Skill --skill pipeline-components --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Pipeline Components?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Pipeline Components
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/vectorspacelab-pipeline-components-86a51be2/badge)](https://www.skillsdirectory.com/skills/vectorspacelab-pipeline-components-86a51be2)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: pipeline-components
description: "Assemble and debug spaCy pipeline components, factories, registry
  wiring, and pipe analysis."
disable-model-invocation: true
metadata:
  disco-role: operating
license: MIT
---

# pipeline-components

Validated against spaCy 3.8.15 on the installed CPU environment. Optional CUDA, Apple, transformer, and language-extra behavior was not verified here.

Use this sub-skill when the task is about `Language.component`, `Language.factory`, `nlp.add_pipe`, component order, registry lookup, source-vs-factory config wiring, or `nlp.analyze_pipes`.

## Read first

- [references/component-factories-and-registry.md](references/component-factories-and-registry.md) for verified `Language.factory` / `Language.component` signatures and component metadata.
- [references/pipeline-assembly-and-analysis.md](references/pipeline-assembly-and-analysis.md) for pipe ordering, enable/disable/select behavior, and `analyze_pipes` usage.
- [references/built-in-components.md](references/built-in-components.md) for the built-in component catalog and what each one roughly does.
- [references/troubleshooting.md](references/troubleshooting.md) when `add_pipe` raises, config validation fails, or a source component gets mistaken for a factory.
- [scripts/inspect_factories.py](scripts/inspect_factories.py) for a safe registry and analysis smoke check.

## What this sub-skill covers

- Registering stateless components with `Language.component`.
- Registering stateful factories with `Language.factory` and default configs.
- Adding components by name, reordering them, and loading components from source pipelines.
- Reading and interpreting built-in factory metadata.
- Using `nlp.analyze_pipes()` to understand assigns/requires/retokenizes relationships.

## What to route elsewhere

- Tokenization, `Doc`/`Token`/`Span`, matchers/rulers, serialization, and displaCy: `documents-and-visualization`.
- `init config`, `debug config`, `train`, `evaluate`, `convert`, `package`, `validate`: `training-and-cli`.
- Install/import or backend concerns: `install-and-inspect`.
- `spacy project` orchestration: `project-workflows`.

## Fast use pattern

1. Check the exact component signature in the reference.
2. Decide whether the user needs a stateless component or a stateful factory.
3. Use the bundled registry inspection script to confirm the named component exists.
4. Read `pipeline-assembly-and-analysis.md` when order, disable/enable, or source-vs-factory confusion appears.

## Evidence basis

This sub-skill is grounded in the installed `Language` signatures, built-in factory source, pipeline tests, and public docs for component registration and pipeline processing.

Files in this skill

  • SKILL.md2.6 KB
  • references/built-in-components.md4.4 KB
  • references/component-factories-and-registry.md4.8 KB
  • references/pipeline-assembly-and-analysis.md6.5 KB
  • references/troubleshooting.md4.1 KB
  • scripts/inspect_factories.py3.4 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…