constraint-parser

Parse scheduling constraints from email text into structured JSON.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/3172973615/skill-explore --skill constraint-parser-3172973615
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: constraint-parser
Source: https://github.com/3172973615/skill-explore/tree/main/skillsbench_subset/tasks/scheduling-email-assistant/environment/skills/constraint-parser
Command: npx skills add https://github.com/3172973615/skill-explore --skill constraint-parser-3172973615

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Parse scheduling constraints from raw email text containing a meeting scheduling request.

Core Features & Use Cases

  • Extract times, time windows, and unavailable periods from natural language emails.
  • Output a structured representation suitable for scheduling engines and conflict resolution.

Quick Start

Provide a sample email containing a meeting request to extract its scheduling constraints.

Frequently Asked Questions about constraint-parser

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

FAQPage Schema
How do I extract meeting scheduling constraints from raw email text?

You can extract meeting scheduling constraints from raw email text by parsing natural language inputs to identify times, time windows, unavailable days, and attendee preferences. This process outputs a structured JSON object containing the constraint types and values for downstream scheduling tools.

What is the best way to parse unavailable times and attendee preferences from emails for a scheduling engine?

The best way to parse unavailable times and attendee preferences from emails is to apply a constraint parser to the raw text. It detects natural language mentions of time windows and unavailability, converting them into a structured representation suitable for conflict resolution by scheduling engines.

Can I use this constraint parser for emails that mention general meeting requests without specific time windows?

This constraint parser is designed for emails that explicitly mention times, time windows, unavailable days, or attendee preferences. If the meeting request lacks specific scheduling constraints, the parser will not be able to extract meaningful structured JSON data for a scheduling engine.

How do I get structured JSON output from emails containing meeting requests and times?

To get structured JSON output from emails containing meeting requests, provide the raw email text to the parser. It analyzes the text for scheduling constraints and outputs a structured JSON object listing the specific constraint types and values extracted from the natural language input.

Does the parser work with natural language emails or does the text need to be pre-formatted?

The parser works directly with natural language emails containing meeting scheduling requests. You provide the raw email text, and it automatically extracts the scheduling constraints without requiring the text to be pre-formatted or structured before input.