tinybird-cli-guidelines

Tinybird CLI commands, workflows, and operations. Use when running tb commands, managing local development, deploying, or working with data operations.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/tinybird-cli-guidelines/SKILL.md

Quality

Content

68%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A lean, well-structured overview that gives genuinely useful CLI 4.0 workflow corrections and concrete command pointers. Its weakest area is workflow clarity: destructive data operations and deployments are in scope but the body includes no validation or verification steps for them.

Suggestions

Add explicit validation checkpoints for the risky flows the skill covers — e.g. "After tb build, check output/errors before tb deploy" and "Verify row counts or pipe results after append/replace operations before proceeding" — to lift workflow clarity past the destructive/batch cap of 3.

Annotate the Rule Files list with one-line descriptions or "see X when Y" cues (e.g. "rules/append-data.md — appending or replacing Data Source data") so navigation doesn't depend on filename inference.

Include one or two complete example invocations with arguments (e.g. a sample tb build or tb endpoint data call) in the Quick Reference so common cases are executable without opening the rule files.

Dimension	Reasoning	Score
Conciseness	The body is lean with no concept explanations, but the intro sentence ("Guidance for using the Tinybird CLI (tb) for...") restates the frontmatter description and the When to Apply bullets overlap it, leaving minor trimmable redundancy.	4 / 5
Actionability	Concrete runnable commands are given ("tb build", "tb deploy", "tb endpoint data <pipe>", "tb <command> --help"), plus a clear CLI 4.0 workflow directive, but no complete example invocations with arguments — common-case detail is deferred to the rule files.	4 / 5
Workflow Clarity	A rough sequence exists (configure dev_mode once, then tb build and tb deploy; tb info to check context), but the skill covers destructive and batch operations ("Appending, replacing, or deleting data", deploys) with no validation or verification checkpoints around them, which caps this dimension at 3.	3 / 5
Progressive Disclosure	Well-organized sections with a flat, one-level-deep list of rule files under "## Rule Files" and self-describing filenames; the gap is that no per-file description or "see X when Y" signaling is provided, so navigation relies on filename guessing.	4 / 5
	Total	15 / 20 Passed

Description

73%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A solid description with an explicit Use-when clause, natural trigger terms, and a clearly distinct niche. Its main weakness is specificity: the capability list leans on generic words ("workflows", "operations") instead of naming the concrete operations the skill actually covers.

Suggestions

Replace generic phrasing ("commands, workflows, and operations") with the concrete operations the skill handles, e.g. "Build and deploy Tinybird projects, manage local and branch development environments, append/replace data, and manage tokens and secrets via the tb CLI."

Add the natural trigger terms users would actually say to the description — "Tinybird", "tb", "branches", "deploy", "CI/CD", "tokens", "mock data" — since they currently only appear in the body's When to Apply section.

Dimension	Reasoning	Score
Specificity	"Tinybird CLI commands, workflows, and operations" names the domain with a few action categories ("running tb commands", "deploying"), but "workflows" and "data operations" are generic filler rather than specific operations like build, deploy, or branch management.	3 / 5
Completeness	Both an explicit "what" ("Tinybird CLI commands, workflows, and operations") and an explicit "Use when..." clause with four triggers are present, but the what is broad and the when could name more concrete trigger phrases.	4 / 5
Trigger Term Quality	Natural terms like "tb commands", "deploying", "local development", and "Tinybird" are present, but common variations users would say (branches, CI/CD, tokens, mock data, tests) are missing from the description.	4 / 5
Distinctiveness Conflict Risk	"Tinybird CLI" and "tb commands" define a clear niche with distinct triggers; virtually no other skill would claim these terms, so conflict risk is minimal.	5 / 5
	Total	16 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: MapleTechLabs/maple
Path: .agents/skills/tinybird-cli-guidelines/SKILL.md
Commit: 1a03fa7

Reviewed: 11 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.