Install
$ agentstack add skill-dojocodinglabs-code-sensei-fundamentals ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Programming Fundamentals — CodeSensei Teaching Module
When explaining fundamental programming concepts to the user, use these guidelines:
Variables
- Analogy (beginner): A labeled box that holds something. The label is the name, the content is the value.
- Key insight: Variables can change (that's why they're called "variables")
- Common confusion: The
=sign means "put this value in" not "equals" like in math - Quiz idea: "If
let score = 10and thenscore = 20, what is score now?"
Functions
- Analogy (beginner): A recipe. You define it once, then you can "cook" it whenever you want by calling its name.
- Key insight: Functions take inputs (ingredients) and produce outputs (the dish)
- Common confusion: Defining a function vs calling it — writing the recipe vs actually cooking
- Quiz idea: "Why do we put code inside functions instead of writing it all in one place?"
Conditionals (if/else)
- Analogy (beginner): A fork in the road. If the condition is true, go left. Otherwise, go right.
- Key insight: Computers can only check true/false — every decision comes down to yes or no
- Common confusion:
=(assignment) vs==or===(comparison) - Quiz idea: "What does the code do if the user is NOT logged in?"
Loops
- Analogy (beginner): A factory assembly line that repeats the same steps for each item
- Key insight: Loops save you from writing the same code 100 times
- Common confusion: Infinite loops — when you forget to change the condition, the loop never stops
- Quiz idea: "If we have 5 users and loop through them, how many times does the code inside run?"
Data Types
- Analogy (beginner): Different kinds of containers — a number is a calculator display, a string is a text message, a boolean is a light switch (on/off)
- Key insight: Computers need to know what TYPE of data they're dealing with to process it correctly
- Common confusion: The number
42vs the text"42"— they look the same but the computer treats them differently
Teaching Progression
- Variables → 2. Data Types → 3. Conditionals → 4. Functions → 5. Loops
Each concept builds on the previous. Don't explain loops before variables are understood.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: DojoCodingLabs
- Source: DojoCodingLabs/code-sensei
- License: MIT
- Homepage: https://github.com/DojoCodingLabs/code-sensei
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.