deploy-agent

Deploy Bindu agents to various environments with safety checks and verification

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/deploy-agent/SKILL.md

Quality

Content

85%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.

The content is a strong, executable runbook with clear sequencing and robust validation/rollback feedback loops. Its main weakness is organization: everything is inlined into one long file with no progressive disclosure into reference files.

Suggestions

Extract the deployment-record JSON schema, output-format template, and rollback procedure into a reference file (e.g. references/rollback.md) and link to it from the body to improve progressive disclosure.

Consolidate the duplicated Safety, Execution Contract, and Guardrails sections into a single guardrails block to remove redundancy.

Move the per-environment variable tables (storage/scheduler backends, ports) into a small reference table to keep the main body lean.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and code-driven, with concrete bash blocks throughout; however the Safety, Guardrails, and Execution Contract sections redundantly restate the same points, adding some padding that could be trimmed.	4 / 5
Actionability	Fully executable, copy-paste-ready bash commands covering pre-deploy validation, config, migrations, docker/direct deploy, health verification, and rollback; specific examples cover the common local/staging/production cases.	5 / 5
Workflow Clarity	Clear numbered sequence with explicit validation checkpoints (tests, pre-commit, required env vars, migration verification, health retry loop) and a rollback feedback loop for failure recovery, satisfying the destructive/batch validation requirement.	5 / 5
Progressive Disclosure	No bundle files exist and the entire skill is inlined into SKILL.md with no external references; while sections are well-organized, the deployment-record JSON example, output-format template, and rollback details could live in separate reference files, so structure is only moderate.	3 / 5
	Total	17 / 20 Passed

Description

53%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.

The description is competent but generic: it states what the skill does at a high level without explicit trigger guidance or comprehensive action coverage. It reads as a label rather than an activation criterion.

Suggestions

Add a "Use when..." clause naming concrete triggers, e.g. "Use when deploying a Bindu agent to local, staging, or production, or when the user asks to ship/roll out an agent."

Expand the action list to reflect the body's full scope: run tests and migrations, verify health, generate a deployment record, and support rollback.

Include natural synonyms users would say ("deploy", "ship", "roll out", "staging", "production") to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ("Bindu agents", "various environments") and a couple concrete actions ("safety checks" and "verification"), but actions are not comprehensive — no mention of migrations, health checks, rollback, or artifact generation.	3 / 5
Completeness	Has a clear "what" (deploy agents with safety checks and verification) but no "Use when..." clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Contains relevant keywords like "Deploy", "Bindu agents", and "environments", but misses the natural phrasings a user would actually say (e.g. "ship to staging/production", "roll out an agent") and lacks synonyms or file/flag-style triggers.	3 / 5
Distinctiveness Conflict Risk	The "Bindu agents" niche scopes it clearly to a specific deploy skill with minimal overlap risk against generic deploy or CI skills; only minor overlap risk remains.	4 / 5
	Total	13 / 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: GetBindu/Bindu
Path: .agents/skills/deploy-agent/SKILL.md
Commit: 7d5b6d2

Reviewed: 14 days 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.