How do I install the Internal Workspace skill?

Run npx skillmds@latest add albumentations-team/internal-workspace in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Internal Workspace safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Internal Workspace?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Internal Workspace free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Internal Workspace?

albumentations-team (@albumentations-team) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Internal Workspace by albumentations-team

Name: Internal Workspace
Author: albumentations-team

Internal Workspace

Use the repo `_internal/` directory for anything that must not be committed — scratch files, temporary outputs, local demos, Codex artifacts, or one-off scripts. Use when creating temp files, debug dumps, or local-only tooling during a task.

File contents

Internal workspace (`_internal/`)

Use it for

Temporary scripts, screenshot/debug exports, large downloaded data, personal benchmark runs, WIP notebooks, and Codex scratch output.
Anything that would otherwise need an ad hoc root-level .gitignore entry.

The directory is ignored and pre-commit rejects staged contents other than _internal/.gitkeep, including files added with git add -f.

Promote durable work

If a file was useful long-term, promote it into the proper place (tools/ for maintained dev scripts, tests/ for permanent tests, or docs/ for documentation) and follow normal review standards — do not leave it in _internal/.

When helping the user

Prefer writing ephemeral or user-specific artifacts to _internal/<descriptive-name>/ rather than the tracked tree.
Removing sensitive or mistaken files from GitHub history requires a history rewrite (e.g. git filter-repo --invert-paths --path ...) and a force push; that is separate from day-to-day use of _internal/ for local junk prevention.

Frequently asked questions