Detect content formats and route them to specialist ingestion skills.
npx skills add https://github.com/rchandnaWUSTL/pm-digital-twin --skill ingest-router
Please help me install this Agent Skill. Skill: Ingest Router Source: https://github.com/rchandnaWUSTL/pm-digital-twin/tree/main/skills/ingest-router Command: npx skills add https://github.com/rchandnaWUSTL/pm-digital-twin --skill ingest-router
This Skill automatically detects the format of raw text content (like Slack threads, RFCs, or signals) and routes it to the appropriate specialized ingestion skill, ensuring consistent structuring and file path management.
Ingest the following content as a Slack thread: "Hey team, let's discuss the new feature launch..."
High-intent search queries and answers about installing and using this skill.
To route Slack threads and RFCs into structured markdown, you need an ingestion pipeline that auto-detects content formats, extracts project tags, generates filesystem-safe slugs, and delegates parsing to specialist skills for consistent file path management.
Structuring unstructured Slack threads and field signals requires a unified ingestion router that applies pattern heuristics to detect content types, generates frontmatter, and saves the data to correct locations with appropriate metadata for analysis.
Content auto-detection for routing semi-structured data like RFCs uses pattern heuristics to identify the source format, extract relevant project tags, and generate collision-free slugs before delegating the content to a specialized ingestion skill.
Yes, you can ingest raw customer emails as field signals. The system identifies the content as a field signal, extracts the customer name and project tags, and saves it to the correct location with appropriate metadata for further analysis.
Yes, the content routing pipeline handles file path collision detection during the ingestion process. It generates filesystem-safe slugs and manages file paths to ensure structured markdown files are saved without overwriting existing data.
You need a unified ingestion pipeline for content processing when handling diverse unstructured and semi-structured formats like Slack threads and RFCs, ensuring they are standardized into structured markdown files with consistent frontmatter and metadata.
paolomozBuild end-to-end data pipelines fetching, analyzing, and visualizing Slack and document intelligence.
ImaginerLabsGenerate sprint-status.yaml from epic and story markdown files.
bettercallfanConvert legal documents into standardized Markdown and remove promotional content.
robotostudioConvert HTML and Markdown content into Portable Text blocks for Sanity.
