terminal
Skill14 starsChanged 8 months agoMITView on GitHub
Command line, npm, git, and shell basics. Activated when Claude runs Bash commands. Demystifies the terminal for non-technical users.
- Reads credentials
- Installs packages
- Commits and pushes
4 other projects use a version of this.
Adopted by
Most recently taken up by
- wonderwhy-er/DesktopCommanderMCPtheir own version, first seen Oct 8, 2026
- samirpatil2000/skillstheir own version, first seen Sep 26, 2026
- zhinkgit/embeddedskillstheir own version, first seen Sep 3, 2026
- wewpellex21/code-senseiword for word, first seen Feb 7, 2026
Other versions4 projects use a version of this.
Word for word · 1
- wewpellex21/code-sensei★ 3100% same
Edited · 0
None found.
Wrote their own version · 3
- wonderwhy-er/DesktopCommanderMCP★ 10ksame name
- zhinkgit/embeddedskills★ 764same name
- samirpatil2000/skills★ 17same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- architectureSkill
- backendSkill
- databasesSkill
- debuggingSkill
- deploymentSkill
- frontendSkill
- fundamentalsSkill
- javascriptSkill
- web-basicsSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 47
⚠️ Teach: NEVER commit .env files to git.
≈ “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.
Files
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 folderls— "List" — see what's in the current folderpwd— "Print Working Directory" — "where am I right now?"- Analogy: You're in a building.
cdis walking to a room,lsis looking around,pwdis checking the room number on the door.
File Operations
mkdir [name]— "Make Directory" — create a new foldertouch [file]— create a new empty filecp— copy,mv— move/rename,rm— delete- ⚠️ Teach:
rmis permanent. There's no trash can.
npm (Node Package Manager)
- Analogy: An app store for code. Other developers built tools and shared them.
npm installdownloads those tools into your project. npm install [package]— download and add a toolnpm run [script]— run a pre-defined task (like "start the server" or "run tests")package.json— the shopping list of all tools your project usesnode_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 descriptiongit 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.
.envfile — 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)
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
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.

