agentleFS
Sign inStart free
danielrosehilldanielrosehill/Claude-Hopper/skills/vscode-here/SKILL.md

vscode-here

Skill1 starsChanged 7 months agoMITView on GitHub

Open VS Code at the current working directory. Use when the user asks to "open in vs code", "open in vscode", "vscode here", or "code .".

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not block waiting on the process.

    line 20
  2. Very specific:

    If code is not on $PATH, fall back to codium or report the missing binary rather than guessing a path.

    line 22

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Open in VS Code

Launch VS Code with the current shell's $PWD as the workspace root. Companion to terminal-here — useful when the user wants to jump from a Claude session into the editor at the same directory.

Command

setsid code "$PWD" >/dev/null 2>&1 &

setsid + background detaches the editor process so it survives after the current Claude Code session exits.

Notes

  • Do not block waiting on the process.
  • Report which directory was opened.
  • If code is not on $PATH, fall back to codium or report the missing binary rather than guessing a path.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free