Individual skill
evo-dialogue-parser
Parses dialogue script text into intermediate section structures using regex, then builds a validated JSON graph schema with typed nodes and edges. Handles section headers, speaker lines, numbered choices with optional tags, and edge targets.
tasks-evolved/dialogue-parser/environment/skills/evo-dialogue-parser/SKILL.md
Source commit 84ca182da055fafb6453dcec4a6defdbbfd987c1
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 99
- Repository last updated
- Sep 10, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- llm-agents Repository topic
- open-world Repository topic
- self-evolving-agents Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 1,090 bytesscripts/__init__.pyruns · 87 bytesscripts/utils.pyruns · 3,531 bytes
Read excerpt
# Dialogue Parser
This skill parses raw dialogue script text files into a structured JSON graph.
## Parsing Rules
- Section headers: `[NodeName]` on their own line
- Speaker lines: `Speaker: text -> Target` (target optional)
- Choice lines: `N. [OptionalTag] Choice text -> Target`
- Node type is "choice" if section has numbered choices, else "line"
## Output Schema
```json
{"nodes": [{"id": str, "text": str, "speaker": str, "type": str}], "edges": [{"from": str, "to": str, "text": str}]}
```