enterprise-agent-ops

Operate long-lived agent workloads with observability, security boundaries, and lifecycle management. Use when running long-lived agent workloads that need observability, security boundaries, or lifecycle control.

Quality

75%

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 ./skills/enterprise-agent-ops/SKILL.md

The canonical home for this skill is tdg-personal/enterprise-agent-ops

Quality

Content

72%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 well-structured and token-efficient with clean sectioning and a clear incident sequence. Its weaknesses are actionability and workflow clarity: the guidance is high-level without concrete executable commands, and the incident workflow lacks an explicit validation feedback loop.

Suggestions

Add concrete executable specifics to the Incident Pattern and Baseline Controls, e.g. example PM2/systemd commands or a sample metric query, so guidance goes from directive-level to copy-paste-ready.

Make the incident feedback loop explicit: after 'run regression + security checks', add 'if any check fails, return to step 4 and re-patch; only resume when all checks pass'.

Replace the generic 'Operate' framing in the intro line with a concrete action verb, or remove the line since it largely restates the frontmatter description.

Dimension	Reasoning	Score
Conciseness	The body is a lean set of terse bullets and a short numbered incident procedure with no padded explanations of concepts Claude already knows; every section adds operational value and assumes Claude's competence.	5 / 5
Actionability	Guidance is specific in spirit ('patch with smallest safe change', 'run regression + security checks') but stays at the directive level with no concrete commands, tool invocations, or metric-query examples, leaving the executable specifics incomplete.	3 / 5
Workflow Clarity	The Incident Pattern is a clear six-step sequence that includes a validation step, but the validate->fix->retry feedback loop is only implicit and there is no explicit checkpoint before resuming rollout in a destructive production context, which caps it at 3.	3 / 5
Progressive Disclosure	The body is under 50 lines, needs no external references, and is organized into clearly headed sections (Operational Domains, Baseline Controls, Metrics, Incident Pattern, Deployment Integrations), satisfying the simple-skill exception for a 5.	5 / 5
	Total	16 / 20 Passed

Description

78%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 strong: it pairs a clear what-statement with an explicit 'Use when' trigger clause and targets a fairly distinct niche. Its main weakness is that the named capabilities are category-level rather than concrete granular actions.

Dimension	Reasoning	Score
Specificity	Names the domain ('long-lived agent workloads') and several capability areas ('observability, security boundaries, and lifecycle management'), but the leading verb 'Operate' is generic and these read as categories rather than concrete granular actions, so it is not comprehensive enough for a 4.	3 / 5
Completeness	It explicitly answers both what ('Operate long-lived agent workloads with observability, security boundaries, and lifecycle management') and when ('Use when running long-lived agent workloads that need observability, security boundaries, or lifecycle control') with a concrete trigger phrase.	5 / 5
Trigger Term Quality	The 'Use when running long-lived agent workloads that need observability, security boundaries, or lifecycle control' clause covers natural domain terms an enterprise user would say; missing common synonyms like 'daemon', 'background process', or 'always-on agent' keeps it just below a 5.	4 / 5
Distinctiveness Conflict Risk	The 'long-lived agent workloads' niche with operational controls is mostly distinct, but generic terms like 'observability' and 'security boundaries' carry minor overlap risk with general devops or observability skills, so it is not a clear 5.	4 / 5
	Total	16 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: skills/enterprise-agent-ops/SKILL.md
Commit: 06c5e11

Reviewed: 3 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.