AC uplo-enterprise-it
AI-powered enterprise IT intelligence spanning DevOps, cybersecurity, and engineering. Unified search across infrastructure, security, and architecture documentation.
As a process C 61/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
ProcedureInfrastructureWriting and documentstype and topics are labelled automatically from the skill text
How to improve
For the model run — optional
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 3
✓ No critical or high findings
Medium and low: 3
-
low Risky intent
intent-offensive-securityidentity-patch.md:7Offensive-security / dual-use content (legitimate for authorised testing; review intended use)When presenting enterprise IT information, include system names, environment contexts, and relevant architecture diagrams or references. Map security controls to the specific systems they protect. For
-
low Risky intent
intent-offensive-securitySKILL.md:12Offensive-security / dual-use content (legitimate for authorised testing; review intended use)Pull your identity context to understand which systems, teams, and clearance tiers you operate within. This determines whether you can access restricted infrastructure documentation like network topol
-
low Risky intent
intent-offensive-securitySKILL.md:89Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- Respect classification tiers strictly in IT contexts. Network architecture diagrams, penetration test results, and API key rotation procedures are typically restricted. If your clearance does not co
Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 61/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 3 mutating operations with no state check
- 100Tools and files. No external tools needed
- 100Steps. 11 steps
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1301 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 166: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 11 items
- +4Has examples (8 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.
External checks
ClawHub: clean
No artifact-backed security concern was available, and the supplied scanner context reports no issues.
LLM: benign (low) · VirusTotal: · 29 May 2026