kazukinagata/analyzing-claude-plugin - Page 2

18-cowork-data-isolation

§2.11 / §2.12. CLI shares CLAUDE_PLUGIN_DATA across sessions; Cowork isolates it per chat session. ROOT remains the same across sessions in both. CLAUDE_CODE_REMOTE is empty in both.

19-cowork-resume

§2.1. Cowork re-fires SessionStart with source=resume after VM suspend. Skill frontmatter hooks reset across the resume. CLI baseline never resumes within one process.

20-cowork-validation

CLI validates plugins fully; Cowork reports a generic Plugin validation failed without exposing the cause (research section 2.3). Runs claude plugin validate on isolated violator variants.

02b-data-in-frontmatter

Intentionally violates §1.2 validator rule by referencing ${CLAUDE_PLUGIN_DATA} in skill frontmatter hook. Expected to be blocked at install time with a "plugin-only" error.

Source text: Mixed languages

02c-userconfig-in-frontmatter

References user_config.KEY in skill frontmatter hook. Validator may pass; /bin/sh should error with Bad substitution at hook execution time.

Source text: Mixed languages

20a-userpromptexpansion

Used by probe 20 to trigger validation rejection on Cowork by including UserPromptExpansion in hooks.

Source text: Japanese

uppercase-skill-name

Used by probe 20 to trigger validation rejection on Cowork via non-kebab-case naming. NOTE this skill folder is named lowercase but the frontmatter name field intentionally violates the rule.

Source text: Mixed languages