agentsclimarketplace

Terminal

Skill DojoCodingLabs/code-sensei/skills/terminal

πŸ₯‹ Claude Code plugin that teaches programming while you vibecode β€” contextual explanations, micro-quizzes, and belt progression. Free & open source by Dojo Coding.

Install
npx -y skills add DojoCodingLabs/code-sensei --skill terminal

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 12 stars12 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Command line, npm, git, and shell basics. Activated when Claude runs Bash commands. Demystifies the terminal for non-technical users.

SKILL.md

2.8 KB, as published. Nobody here has run it

Terminal & Command Line β€” CodeSensei Teaching Module

The Terminal

  • Analogy: The terminal is like texting your computer. Instead of clicking buttons, you type instructions and it responds. It's not scarier than that.
  • Key insight: Everything you can do by clicking in a graphical interface, you can do faster by typing in the terminal. Developers prefer typing because it's faster and scriptable.

Essential Commands

Teach these as they appear in the user's session:

Navigation

  • cd [folder] β€” "Change Directory" β€” walk into a folder
  • ls β€” "List" β€” see what's in the current folder
  • pwd β€” "Print Working Directory" β€” "where am I right now?"
  • Analogy: You're in a building. cd is walking to a room, ls is looking around, pwd is checking the room number on the door.

File Operations

  • mkdir [name] β€” "Make Directory" β€” create a new folder
  • touch [file] β€” create a new empty file
  • cp β€” copy, mv β€” move/rename, rm β€” delete
  • ⚠️ Teach: rm is permanent. There's no trash can.

npm (Node Package Manager)

  • Analogy: An app store for code. Other developers built tools and shared them. npm install downloads those tools into your project.
  • npm install [package] β€” download and add a tool
  • npm run [script] β€” run a pre-defined task (like "start the server" or "run tests")
  • package.json β€” the shopping list of all tools your project uses
  • node_modules/ β€” the warehouse where downloaded tools live (never edit this!)

git (Version Control)

  • Analogy: A time machine for your code. Every "commit" is a save point you can go back to.
  • git add β€” stage changes (put items on the "to save" pile)
  • git commit β€” save a snapshot with a description
  • git push β€” upload your snapshots to the cloud (GitHub)
  • git pull β€” download the latest from the cloud
  • Key insight: Git exists because code breaks. It lets you undo mistakes by going back to when things worked.

Environment Variables

  • Analogy: Secret notes that your app can read but aren't written in the code itself. Like a password you whisper instead of writing on a whiteboard.
  • .env file β€” where secrets live (API keys, database passwords)
  • ⚠️ Teach: NEVER commit .env files to git. That's like posting your passwords publicly.

Scary-Looking but Simple

  • | (pipe) β€” sends output from one command as input to another, like a conveyor belt
  • > β€” saves output to a file instead of showing it on screen
  • && β€” "do this AND THEN do that" (run two commands in sequence)
  • sudo β€” "do this as administrator" (the master key)

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.