tally

Automate Tally form CRUD, submission export, and webhook delivery via CLI.

6|1|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/cathrynlavery/tally-skill --skill tally
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tally
Source: https://github.com/cathrynlavery/tally-skill/tree/main
Command: npx skills add https://github.com/cathrynlavery/tally-skill --skill tally

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

It eliminates the need to manually click through Tally to create forms, inspect questions, export submissions, and set up webhook delivery for downstream workflows.

Core Features & Use Cases

  • Create and update forms from the terminal: generate simple forms using a label=type DSL or build multi-page forms from a JSON blocks file.
  • Read and export submission data: list submissions, fetch individual responses, and export results as safe CSV or JSON for pipelines and analysis.
  • Automate webhook workflows: create, list, inspect events/delivery history, and retry failed webhook deliveries.

Quick Start

Run tally form create-simple with your form name and fields in the --fields DSL, then check delivery by creating a webhook for the new form ID and exporting submissions as safe CSV.

Frequently Asked Questions about tally

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

FAQPage Schema
How do I automate Tally form creation and submission exports from the terminal?

Tally form automation is handled through a terminal-first CLI that creates or updates form structures, reads submission data, and exports results as safe CSV or JSON. You can generate simple forms using a label=type DSL or build multi-page forms from a JSON blocks file.

Can I manage Tally webhook delivery and retry failed webhooks programmatically?

Yes, Tally webhook management is fully supported via the CLI. You can create webhooks, list active subscriptions, inspect event delivery history, and retry failed webhook deliveries directly from the terminal for downstream workflow automation.

Do I need a specific API key to authenticate Tally REST API calls for form management?

You need a TALLY_API_KEY to authenticate REST API calls to Tally endpoints for form and submission CRUD operations. If the key is not found, the system can fall back to retrieving it from a 1Password integration.

What is the best way to export Tally submissions as CSV for data pipelines?

Exporting Tally submissions as safe CSV is a core CLI feature. You can list submissions, fetch individual responses, and export the results directly as CSV or JSON, producing agent-friendly JSON envelopes with validation safeguards for pipeline ingestion.

Does the Tally CLI work with agent-friendly JSON output for automated workflows?

Yes, the CLI returns agent-friendly JSON envelopes containing ok or error statuses, plus next_actions and validation safeguards. This structure is designed for programmatic CRUD operations and seamless integration into automated agent workflows.

What are the limitations of using a CLI for Tally form automation instead of the web interface?

The CLI requires YAML-defined skill entries and authenticated REST API access. While it excels at programmatic CRUD and webhook lifecycle management, users needing visual form editing or real-time drag-and-drop building may find the terminal-first approach less interactive.