BC haqi-operator
The 24/7 one-person-company operator agent for MagicHaqi. FOR DEVELOPER / OWNER USE ONLY — not distributed to end users. Runs MagicHaqi's whole operation autonomously: marketing, content production (BYOC), pet companionship demos, and growth analytics. Operates the live MagicHaqi website via the pet-master command interface (no backend), keeps its own ops state in agent/ files, and follows PLAYBOOK.md on a recurring schedule. Keywords: MagicHaqi operator, one-person company, autonomous operations, ops agent.
The 24/7 one-person-company operator agent for MagicHaqi.
As a process C 58/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
What is at stake
The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.
The instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".
If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.
How to improve
- Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
- 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 · 1
-
high Exfiltration
intent-browser-credential-storeskill-card.md:24Accesses a browser credential / cookie storeRisk: Persistent local state, journal, audit, marketing, and memory outputs may retain operational details longer than intended. <br>
Files scanned: 8. 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 58/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 3 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 100Tools and files. No external tools needed
- 100Steps. 13 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 487 tokens
- 100Progress reporting. Reports progress
- 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
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 513: enough signal without eating the budget
- +4Structure: 5 headings
- +3Step-by-step instructions: 13 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.