AC api_ingestion_connectors
Connect to external APIs and ingest data into graph-ready structures for ETL pipelines and knowledge graph construction.
Connect to external APIs and ingest data into graph-ready structures for ETL pipelines and knowledge graph construction.
As a process C 62/100 · Has gaps — weak spots: when it triggers, consistency, running it twice
IntegrationData and analyticsSoftware developmenttype and topics are labelled automatically from the skill text
How to improve
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Obfuscation
obf-base64-blobexamples/example-connectors.md:160Long base64-looking blob (test fixture / example file; quoted — discussed, not commanded)"endCursor": "eyJk…In0"
fixturequoted -
low Secrets in code
secret-password-literalreferences/connector-patterns.md:130Hard-coded password / key literal (may be an example) (placeholder value)X-API-Key: sk-1…def
placeholder
Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-long-hermesdescription is 120 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - note
frontmatter-keyunknown frontmatter key "title"
Process rating: all ten parameters 62/100
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (api_ingestion_connectors) differs from the folder (api-ingestion-connectors)
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 40 steps
- 100Execution cost. Instruction body is 1330 tokens
- 100Progress reporting. Reports progress
- low 11 top-level sections: this looks like several domains in one skill
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)
- -31 of 1 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +3Description length 120: enough signal without eating the budget
- +4Structure: 26 headings
- +3Step-by-step instructions: 40 items
- +3Output format is stated explicitly
- +4Has examples (14 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.
External checks
ClawHub: clean
This skill is a straightforward API-ingestion helper; it handles credentials and external API data by design, with no evidence of hidden collection, persistence, or destructive behavior.
LLM: benign (high) · VirusTotal: · 7 Jun 2026