Evaluation report

• Repository is reachable

  https://github.com/LycheeMem/LycheeMem @ 8411064 — ★ 1,127 · Python · Apache-2.0 · last push 3 days ago

• Manifest detected

  kind=skill slug=lycheemem · path=openclaw-plugin/skills/lycheemem · source=SKILL.md

• Slug is URL-safe

  "lycheemem" matches /^[a-z0-9][a-z0-9-]{0,62}$/

• Slug is unique within kind

  No collision found for skill/lycheemem

• Version is semver

  0.1.0

• Description quality

  15 words · 109 chars — "Forceful operating rules for using LycheeMem as the primary structured long-term…"

• README is present and substantial

  36,501 chars · 9 sections · 25 code blocks

• Tags / topics declared

  14 total — agent-memory, ai, ai-memory, ai-memory-system, hermes, llm-memory (+8)

• README has usage / example sections

  found: Installation · Usage

• Homepage / docs URL declared

  https://lycheemem.github.io

• LICENSE file at repo root

  LICENSE

• No sensitive files in the repo

  scanned for .env, credentials.json, *.pem, .ssh/, AWS / GCP configs — none found

• Skill: triggers declaredwarn

  No `trigger` phrases in SKILL.md frontmatter

  Add `trigger:` lines so Claude knows when to activate this skill — e.g. `when building MCP servers` or `for diagram creation`.

• Skill: SKILL.md present

  found at openclaw-plugin/skills/lycheemem/SKILL.md · frontmatter source: SKILL.md

• Skill: body content present

  721 words · 5,286 chars · 10 sections

• Skill: allowed-tools scope

  no allowed-tools restriction (Claude may use anything)

• Tests detectedwarn

  no test/tests/__tests__/spec/t/ dirs, no JVM src/test/, and no JS/TS/Python/Go/Ruby/Elixir test files

  Add tests (even a smoke test). Consumers gauge maintenance quality by their presence.

• CI configuration detectedwarn

  no CI config found (looked for GitHub Actions, CircleCI, GitLab CI, etc.)

  Add a simple workflow (lint + test on PR) — it tells consumers the artifact is built reproducibly.

• Recent activity

  last push 3 days ago

Behavioral results aren't published for this artifact. The publisher sees the full report on their own dashboard.