jason/chorus
1
0
Fork 0
forked from jason/echo
Code Pull Requests Activity

Fix SKILL.md description over marketplace 1024-char cap + build guard

Browse Source 
The plugin upload validates each skills/**/SKILL.md `description` frontmatter
against a 1024-char cap (distinct from plugin.json's <500 rule). The skill
description was 1171 chars and got rejected on upload.

- Trim the chorus-memory SKILL.md description to 1000 chars, preserving the
  save/recall/group triggers and the full "Do NOT" exclusion list.
- Add MAX_SKILL_DESCRIPTION=1024 guard to build.py: scans every SKILL.md and
  fails the build with an over-by-N message so this can't silently regress.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
Jason Stedwell
2026-07-25 00:03:05 -05:00
parent f2bfd70dd4
commit 6b538bbb87
2 changed files with 34 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
chorus-memory.plugin.src/skills/chorus-memory/SKILL.md
+1 -1
View File
@@ -1,6 +1,6 @@
---
name: chorus-memory
description: Use the shared CHORUS Obsidian vault as the group's persistent memory across Claude/CoWork sessions — one vault, many members, every write attributed to the configured member. Use whenever the member asks to remember, save, note, log, or capture anything durable — facts, preferences, decisions, schedule changes, commitments — or asks what Claude knows about them or the team, what was discussed or decided before (by anyone in the group), to check their notes, load their memory/profile/context, add to their or the group's inbox, to see what other members have been working on, or to track a new project. Trigger even without memory phrasing when the request implies recalling or persisting state across sessions ("pick up where we left off", "anything on X before my meeting?", "did anyone already look into this?"). Also use proactively at the start of substantive work sessions to load context and at the end to log outcomes. Do NOT use for vaults outside this group, Obsidian/REST-API development questions, "memory" meaning RAM, timed reminders, email or local-file lookups, generic second-brain advice, or notes the member routes to a specific other file or app.
description: Use the shared CHORUS Obsidian vault as the group's persistent memory across Claude/CoWork sessions — one vault, many members, every write attributed to its member. Use whenever a member asks to remember, save, note, log, or capture anything durable — facts, preferences, decisions, commitments — or asks what Claude knows about them or the team, what was discussed or decided before, to check notes, load memory/profile/context, add to an inbox, or see what other members are working on. Trigger even without memory phrasing when the request implies recalling or persisting state across sessions ("pick up where we left off", "did anyone already look into this?"). Also use proactively at the start of a session to load context and at the end to log outcomes. Do NOT use for vaults outside this group, Obsidian/REST-API development questions, "memory" meaning RAM, timed reminders, email or local-file lookups, generic second-brain advice, or notes the member routes to a specific other file or app.
---
# CHORUS Memory