Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/cx18121-algorithms-homework
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
Network hosts it talks to 1
codeload.github.com· found in install command
Files it touches
~/.claude/skills/algorithms-homework
What's inside
- Skill name
algorithms-homework- Description
- Guided help for Charlie's algorithms coursework.
- License
- MIT
- Instructions
- 39 lines in SKILL.md · view on GitHub
Files (1)
- SKILL.md
SKILL.md (first lines)
# Algorithms Homework
Read the exact problem and Charlie's current work before judging an idea.
## Tutor
When Charlie is stuck or asks how to start, give one small hint or guiding question. Wait for his response before giving the next step. Answer factual questions directly without revealing the rest of the solution.
Build from Charlie's reasoning. Say whether the core idea is right, then identify the exact missing or incorrect step. Distinguish a logical problem from wording that is merely unclear.
Write a complete solution or edit the LaTeX file only after an explicit request such as "write it up" or "add it."
## Review
Check every requirement in the problem.
For induction, verify the statement, base case, induction hypothesis, induction step, and conclusion.
For an algorithm, verify the inputs, steps, output, correctness argument, and running-time analysis. Make sure every recursive call or loop preserves the conditions needed by the proof.
Use an instructor style guide when one is provided. Prefer a concise explanation that Charlie and the grader can follow on the first read. Keep every important justification even when a shorter proof is possible.
## Style
Follow the problem numbering with headings such as `\textbf{1a.}`. For algorithm questions, organize the answer under `\textbf{Algorithm:}`, `\textbf{Correctness:}`, and `\textbf{Running time:}`.
When revising an existing answer, use Charlie's draft as the main style sample. Keep as much of his wording as possible and make the smallest change that fixes the mathematical issue. When writing an answer from scratch, read one or two of Charlie's completed answers from the same course when available. If no sample exists, use short direct sentences, familiar wording, minimal notation, and a proof structure that follows his reasoning in order.
Match Charlie's vocabulary, sentence length, proof structure, and level of formality. Write direct paragraphs that follow his reasoning in order. State what the algorithm does before proving it. In a proof, explain why each step preserves the required condition. Use displayed equations when they carry part of the argument, not as decoration.
Prefer notation already used by the problem. When new notation is needed, give it a descriptive name, define it immediately, and keep its role small. Prefer a few extra plain sentences over compressed symbolic arguments or a more formal proof style than Charlie uses.
Write the AI acknowledgment in Charlie's first-person style and describe the actual help precisely.
## Write up
When editing an assignment, change only the requested section. Keep any required AI acknowledgment accurate. Compile the current LaTeX source and fix errors before reporting completion.From cx18121/agent-skills, MIT.
More from cx18121/agent-skills
- 0.561score
better-interface
cx18121
Review UI screens, flows, branches, or PRs across design domains.
SkillAFreshness: AClaude Code +9 - 0.561score
firecrawl
cx18121
Use Firecrawl for an explicit Firecrawl request, site mapping, bulk crawling, structured web extraction, or live page interaction that the native web and…
SkillAFreshness: AClaude Code +9 - 0.550score
idiot
cx18121
Explain from zero context in simple, concise terms.
SkillAFreshness: AClaude Code +9 - 0.539score
codebase-design
cx18121
Shared vocabulary for designing deep modules.
SkillAFreshness: AClaude Code +9 - 0.539score
herdr
cx18121
Use only when the user explicitly mentions Herdr or requests its pane, tab, workspace, command, or agent controls.
SkillAFreshness: AClaude Code +9 - 0.524score
diagnosing-bugs
cx18121
Reproduction signals, chronology, and hypothesis testing for hard, elusive, or intermittent bugs.
SkillBFreshness: BClaude Code +9 - 0.521score
apple-design
cx18121
Use for gesture-driven and physics-based interaction, springs, drag and swipe behavior, sheets, momentum, interruption, and Apple material or depth effects.
SkillBFreshness: BClaude Code +9 - 0.519score
eli5
cx18121
Explain a topic like I'm a 5 year old.
SkillBFreshness: BClaude Code +9 - 0.519score
docker-cleanup
cx18121
Use when Charlie asks to free local Docker or OrbStack disk, remove unused containers, images, volumes, networks, or build cache, or diagnose recurring Docker…
SkillBFreshness: BClaude Code +9 - 0.515score
emil-design-eng
cx18121
Emil Kowalski's technique reference for component behavior, CSS transforms, clip-path, gestures, and animation performance.
SkillBFreshness: BClaude Code +9 - 0.513score
commit-style
cx18121
Mandatory when writing, amending, squashing, or proposing a commit subject or pull request title.
SkillBFreshness: BClaude Code +9
Signals
- Stars
- 0
- Forks
- 0
- Open issues
- 0
- Last commit (this folder)
- Sep 14, 2026 (1 month ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- MIT
- Repository
- github.com/cx18121/agent-skills
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
More from cx18121
- 0.561score
better-interface
cx18121
Review UI screens, flows, branches, or PRs across design domains.
SkillAFreshness: AClaude Code +9 - 0.561score
firecrawl
cx18121
Use Firecrawl for an explicit Firecrawl request, site mapping, bulk crawling, structured web extraction, or live page interaction that the native web and…
SkillAFreshness: AClaude Code +9 - 0.550score
idiot
cx18121
Explain from zero context in simple, concise terms.
SkillAFreshness: AClaude Code +9 - 0.539score
codebase-design
cx18121
Shared vocabulary for designing deep modules.
SkillAFreshness: AClaude Code +9 - 0.539score
herdr
cx18121
Use only when the user explicitly mentions Herdr or requests its pane, tab, workspace, command, or agent controls.
SkillAFreshness: AClaude Code +9 - 0.524score
diagnosing-bugs
cx18121
Reproduction signals, chronology, and hypothesis testing for hard, elusive, or intermittent bugs.
SkillBFreshness: BClaude Code +9
Cite this page
algorithms-homework skill. Agent Mart. https://agentmart.dev/skills/cx18121-algorithms-homework (last updated 2026-10-24)