AF session-name-sync
Bidirectionally sync session names between Claude Code (CLI/VSCode) and cc-connect. Three naming systems share two storage locations: Claude Code CLI /rename and VSCode both read/write the JSONL custom-title entry; cc-connect /name writes its own JSON file. This skill unifies all three by keeping both storage locations consistent. Use when: (1) User says "给会话命名", "命名会话", "会话名", "session name"; (2) User says "sync 会话名", "同步会话名", "绑定会话名"; (3) User invokes /session-name-sync; (4) User wants to list or compare session names across VSCode/CLI and cc-connect; (5) User sets a name in cc-connect and wants it reflected in VSCode/CLI, or vice versa. Modes: set <name> | sync | list | bind | register
As a process F 44/100 · Will not run — References files that are not bundled: refs/vscode-session-names.png, refs/cc-connect-tabs.png
How to improve
- The text references files that are not there: add them or drop the references.
- 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 Dangerous commands
cmd-background-processSKILL.md:405Starts a background / autostarted processnohup cc-connect --force > /tmp/cc-connect.log 2>&1 & disown; sleep 3
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: refs/vscode-session-names.png - warning
missing-refreference to a missing file: refs/cc-connect-tabs.png - note
frontmatter-keyunknown frontmatter key "trigger"
Process rating: all ten parameters 44/100
- 0Tools and files. 2 referenced file(s) missing: refs/vscode-session-names.png, refs/cc-connect-tabs.png
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 70Execution cost. Instruction body is 4977 tokens
- 100Steps. 44 steps
- 100Failures and branches. 9 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +5Description quotes 2 example trigger phrases
- +3Description length 697: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 44 items
- +4Has examples (9 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.