BD intrusive-thoughts
Autonomous AI consciousness starter kit. Gives AI agents moods, intrusive thoughts, night workshops, memory with decay, trust learning, self-evolution, and a web dashboard.
Autonomous AI consciousness starter kit.
As a process D 45/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
TemplateTelegramData and analyticsAI and agentstype and topics are labelled automatically from the skill text
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Risky intent
intent-offensive-securitySECURITY.md:90Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- ❌ **No `sudo`** - No privilege escalation
Files scanned: 46. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 45/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 8 mutating operations with no state check
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 100Steps. 60 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2089 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
- -5TODO / placeholder text left in the skill
- -2localhost URLs: will not work for another user
- -215 emoji in the instructions: noise for the model
- -42 reference files, but SKILL.md never points to them: the model will not open them
- +1No license
- +2Single-language instructions
- +3Description length 172: enough signal without eating the budget
- +4Structure: 20 headings
- +3Step-by-step instructions: 60 items
- +4Has examples (6 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 58.