Tolaria Wrap Automation

Problem

When working with Markdown and TypeScript in a repository, the issue is rarely a missing script. It is usually that docs, build entry points, and GitHub workflows need a clearer shared wrapper. The available tags are wrap, github, and automation, suggesting that Tolaria Wrap targets scenarios where scattered steps need to be consolidated into a reusable entry point: keeping Markdown readable while giving TypeScript workflows a clearer boundary. If the goal is to let teams inspect docs, trigger scripts, and reuse process steps from the same entry point, this kind of wrapper fits engineering habits better than copying commands individually.

How it works

Based on the readable metadata, it looks more like a lightweight wrapper than a complete business system:
- Positioning: provides a skill entry point around Markdown and TypeScript related flows
- Context: tags point to GitHub and automation, so it fits attaching existing steps into a workflow
- Usage: confirm inputs, outputs, and dependencies first, then decide whether it is suitable for doc cleanup, script wrapping, or pipeline experiments

Boundaries

Because the SKILL.md body has limited readable detail, this does not assume specific commands, APIs, or generation logic. It is suitable for process exploration, wrapper experiments, and automation entry validation; avoid production changes before permissions, script dependencies, and input formats are confirmed.