tinybird-cli-guidelines

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

Quality

93%

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

Quality

Content

87%

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

The body is a tight, well-organized overview that delegates depth to a flat set of rule files and provides concrete executable commands. Its only gap is the absence of explicit validation checkpoints for the destructive data operations it references, which caps workflow clarity at level 2.

Suggestions

Add a short validation/verification note in the Quick Reference for destructive and batch data operations (e.g., 'Verify row counts with tb info before/after tb append or replace; never delete without confirming the target Data Source').

Surface at least one feedback-loop cue (run tb <command> --help or tb info to confirm context after risky ops) so destructive workflows have an explicit checkpoint in the body rather than only in the rule files.

Dimension	Reasoning	Score
Conciseness	The body is lean and dense — terse bullet lists, a one-line summary, and no explanation of concepts Claude already knows — so every token earns its place, matching the level-3 'lean and efficient' anchor rather than level-2 'some unnecessary explanation'.	3 / 3
Actionability	It gives concrete, copy-paste-ready commands ('tb build', 'tb deploy', 'tb info', 'tb endpoint data <pipe>', 'tb <command> --help') and specific flags, matching the level-3 'fully executable commands' anchor.	3 / 3
Workflow Clarity	A clear sequence is present (configure dev_mode once, then tb build/tb deploy), but destructive batch operations like appending, replacing, and deleting data are listed with no validation checkpoints in the body, capping this at level-2 per the destructive-operations guideline rather than level-3's explicit validation steps.	2 / 3
Progressive Disclosure	The body is a concise overview split into named sections with a flat, one-level-deep 'Rule Files' list and a 'Quick Reference', matching the level-3 'clear overview with well-signaled one-level-deep references' anchor rather than level-2's poorly-signaled or inline-heavy structure.	3 / 3
	Total	11 / 12 Passed

Description

100%

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

The description is concise yet complete, explicitly stating both what the skill does and when to use it with natural trigger phrasing and a distinct, well-scoped niche. It hits the top anchor on every dimension.

Dimension	Reasoning	Score
Specificity	Names the Tinybird CLI domain plus several concrete actions ('running tb commands, managing local development, deploying, or working with data operations'), matching the 'multiple specific concrete actions' anchor rather than the level-2 'some actions but not comprehensive'.	3 / 3
Completeness	It explicitly answers both what ('Tinybird CLI commands, workflows, and operations') and when ('Use when running tb commands...'), with an explicit trigger clause, matching the level-3 anchor.	3 / 3
Trigger Term Quality	Natural user phrasing like 'running tb commands', 'managing local development', and 'deploying' are terms users would actually say, giving good coverage rather than the level-2 'some relevant keywords but missing common variations'.	3 / 3
Distinctiveness Conflict Risk	The description is scoped to the distinct niche of the Tinybird CLI with clear, narrow triggers, making it unlikely to fire for an unrelated skill.	3 / 3
	Total	12 / 12 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: 8d347f8

Reviewed: about 13 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.