.claude/skills/workspace-structureRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
Maintain a clean workspace file structure. Use when deciding where files and folders belong in a workspace, choosing temporary vs. durable storage, or distinguishing projects, installed apps, tools, scripts, data stores, user files, reports, sources, reference material, and entertainment.
These states come from the source or distribution context. None of the entries below are SkillVetAI compatibility test results.
These checks parse the fixed package against dated platform rules. They do not execute the Skill or verify task behavior.
.claude/skills/workspace-structureRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
.agents/skills/workspace-structureRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
skills/workspace-structureRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
This command is recorded from the source ecosystem and resolves the registry's latest release. The fixed release shown on this page should be inspected before adoption.
clawhub install @synbraino/workspace-structureclawhub inspect @synbraino/workspace-structure --version 1.1.0This automated, non-executing scan is bound to this release hash. It is not a safety certification and may contain false positives or false negatives.
This is registry-supplied evidence for the recorded release, not an independent SkillVetAI scan. Check the canonical source for the full report, scanner versions, scope, and current moderation state.
The catalog stores hashes and an inventory summary for change detection. It does not republish the package contents.
sha256:3cac7b617ddb51df15286884010b9892f8d170a498e3bd367b530a3b50b39cb3references/edge-cases.mdreferences/folder-taxonomy.mdreferences/naming-and-structure.mdskill-card.mdSKILL.md- Added apps/ for operational application installations. - Separated development materials from operational installations and working data. - Clarified boundaries between apps/, projects/, tools/, scripts/, data/, and user-files/. - Added guidance to preserve persistent data during release updates and keep test data separate. - Refined placement rules and examples, reduced duplication, and improved wording.