SKILLEMALL.ai
GitHub ↗ RU Sign in

BD limitless_lifelogs

Search, summarize, and extract insights from your Limitless AI pendant life logs. Supports keyword and semantic search, date range queries, memory recall, and action item extraction for named agents.

modbender/skill-library-mcp Agent Skills author: modbender MIT 3 files · 1 script body ≈ 1 713 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Search, summarize, and extract insights from your Limitless AI pendant life logs.

As a process D 48/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

IntegrationWriting and documentsAI and agentstype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
78/100
safety, quality, tests
Safety 60%
85
Quality 40%
67
Run on models
none yet
Process rating
D
48/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Dangerous commands medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.

For the author

Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.

Exfiltration medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

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".

For the author

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

  1. 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 · 3

✓ No critical or high findings

Medium and low: 3
  • medium Dangerous commands cmd-shell-rc install.sh:30
    Writes to a shell startup file
    echo "       # Add to ~/.zshrc or ~/.bashrc to persist it."
  • medium Exfiltration net-credential-use SKILL.md:38
    Credential used in a network call (verify the destination is the intended service)
    curl -s -H "X-API-Key: $LIMITLESS_API_KEY" \
  • medium Exfiltration net-credential-use SKILL.md:59
    Credential used in a network call (verify the destination is the intended service)
    curl -s -H "X-API-Key: $LIMITLESS_API_KEY" \

Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)
  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 48/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. 9 mutating operations with no state check
  • 40Consistency. Frontmatter name (limitless_lifelogs) differs from the folder (limitless-lifelogs)
  • 60Tools and files. Uses tools (web) that frontmatter does not declare
  • 85Steps. 26 steps, 2 vague phrases
  • 100Failures and branches. 2 branches, has a failure section
  • 100Execution cost. Instruction body is 1713 tokens
  • 100Progress reporting. Reports progress
  • low The response is described with custom markup (5 tags): a typed call is more reliable

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 199: enough signal without eating the budget
  • +4Structure: 13 headings
  • +3Step-by-step instructions: 26 items
  • +4Has examples (7 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.