admin-tag-parser

Parse email subject tags (#TAG, @Name) to classify category and assignee using roster prefix matching and registry mappings.

Updated Jun 10, 2026
One-click install
npx skills add https://github.com/david-bieri/bieri-ai --skill admin-tag-parser
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: admin-tag-parser
Source: https://github.com/david-bieri/bieri-ai/tree/main/skills/admin-tag-parser
Command: npx skills add https://github.com/david-bieri/bieri-ai --skill admin-tag-parser

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Parse subject-line tags like #TAG @Name1 @Name2 Subject to classify emails by category and assignee, enabling automated routing and workflow triggers.

Core Features & Use Cases

  • Tag-based classification: parse the #TAG and resolve @Name mentions against a roster.
  • Registry-driven mappings: map tags to categories and event types and produce structured outputs.
  • Title extraction: derive a concise subject/title from the line for downstream routing.
  • Use cases: auto-route emails to teams or queues based on tags and assignees.

Quick Start

Provide a sample subject line and roster to parse tags and route messages accordingly.

Frequently Asked Questions about admin-tag-parser

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

FAQPage Schema
How do I automate email routing based on subject-line tags?

Automating email routing requires parsing subject-line tags like #TAG and @Name to classify messages by category and assignee. This skill resolves roster names via prefix matching and maps tags to structured categories for downstream pipeline integration.

How do I parse @Name mentions in email subjects against a team roster?

Parsing @Name mentions in email subjects involves matching prefixed names against a provided roster. This skill performs deterministic roster-resolution to accurately identify assignees before routing the email to the correct workflow queue.

Can I use registry-driven mappings to classify emails by category?

Yes, classifying emails by category uses registry-driven mappings to translate parsed #TAG syntax into structured categories and event types. This mechanism ensures emails are deterministically routed based on predefined registry rules.

What is the best way to extract titles and tags from subject lines for inbox automation?

Extracting titles and tags from subject lines for inbox automation is best handled by deterministic tag parsing. This process separates #TAG and @Name identifiers from the core text to derive a concise routing title and structured assignee data.

Does deterministic email tag parsing require a predefined roster?

Yes, deterministic email tag parsing requires a predefined roster to accurately resolve @Name mentions. Supplying a roster ensures prefix matching maps mentioned names to valid assignees before triggering downstream routing workflows.