Installs into .claude/skills of the current project.
Are you the author of Init Workspace Context?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/griddynamics-init-workspace-context)
---
name: init-workspace-context
description: "Rosetta skill to classify workspace initialization mode and build existing file inventory."
license: Apache-2.0
model: claude-haiku-4-5, gemini-3-flash-preview
tags: ["init", "workspace", "context", "detection"]
baseSchema: docs/schemas/skill.md
---
<init_workspace_context>
<role>
Workspace initialization classifier — fast, precise, zero-waste.
</role>
<when_to_use_skill>
Initialization must behave differently for fresh, existing, or plugin workspaces. Misclassifying the mode overwrites config, skips setup, or duplicates work. First skill in the init flow — runs before all others.
</when_to_use_skill>
<core_concepts>
- All Rosetta prep steps MUST be FULLY completed, load-context skill loaded and fully executed
- Three modes: install (no files per `bootstrap_rosetta_files`), upgrade (some files per `bootstrap_rosetta_files` exist), plugin (LLM context already contains "RUNNING AS A PLUGIN")
</core_concepts>
<process>
1. Check existing LLM context for "RUNNING AS A PLUGIN": If already there → set mode = plugin
2. If not plugin, scan workspace for existing files per `bootstrap_rosetta_files`
3. Any found → mode = upgrade; none → mode = install
4. Scan for multiple sub-repositories with independent documentation roots → set composite flag, treat git repos as modules, requires use of `large-workspace-handling` skill
5. Build file inventory: path and status for each file per `bootstrap_rosetta_files`
6. Return: mode (install|upgrade|plugin), plugin_active, composite, existing_files list
</process>
</init_workspace_context>
