DeepTutor CLI
HKUDS/DeepTutor
Teaches the agent to set up and run DeepTutor from the command line: chat and capabilities, knowledge bases, partners, memory, sessions, notebooks and the server or Web app.
Build an interactive report or experiment when the user asks to explore model capabilities.
$ npx skills add jellydn/my-ai-tools --skill capability-experiments -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jellydn/my-ai-tools capability-experiments --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jellydn/my-ai-tools.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/capability-experiments .claude/skills/capability-experiments && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "capability-experiments" agent skill from https://github.com/jellydn/my-ai-tools/tree/main/skills/capability-experiments into .claude/skills/capability-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "capability-experiments", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jellydn/my-ai-tools/tree/main/skills/capability-experimentsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jellydn/my-ai-tools --skill capability-experiments -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jellydn/my-ai-tools capability-experiments --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jellydn/my-ai-tools.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/capability-experiments .agents/skills/capability-experiments && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "capability-experiments" agent skill from https://github.com/jellydn/my-ai-tools/tree/main/skills/capability-experiments into .agents/skills/capability-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "capability-experiments", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jellydn/my-ai-tools --skill capability-experiments -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jellydn/my-ai-tools capability-experiments --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jellydn/my-ai-tools.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/capability-experiments .cursor/skills/capability-experiments && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "capability-experiments" agent skill from https://github.com/jellydn/my-ai-tools/tree/main/skills/capability-experiments into .cursor/skills/capability-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "capability-experiments", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jellydn/my-ai-tools.git --path skills/capability-experiments--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jellydn/my-ai-tools --skill capability-experiments -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jellydn/my-ai-tools capability-experiments --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jellydn/my-ai-tools.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/capability-experiments .gemini/skills/capability-experiments && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "capability-experiments" agent skill from https://github.com/jellydn/my-ai-tools/tree/main/skills/capability-experiments into .gemini/skills/capability-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "capability-experiments", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jellydn/my-ai-tools capability-experimentsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jellydn/my-ai-tools --skill capability-experiments -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jellydn/my-ai-tools.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/capability-experiments .github/skills/capability-experiments && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "capability-experiments" agent skill from https://github.com/jellydn/my-ai-tools/tree/main/skills/capability-experiments into .github/skills/capability-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "capability-experiments", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jellydn/my-ai-tools --skill capability-experiments -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jellydn/my-ai-tools capability-experiments --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jellydn/my-ai-tools.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/capability-experiments .opencode/skills/capability-experiments && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "capability-experiments" agent skill from https://github.com/jellydn/my-ai-tools/tree/main/skills/capability-experiments into .opencode/skills/capability-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "capability-experiments", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
capability-experimentsBuild an interactive report or experiment when the user asks to explore model capabilities.
Capability Experiments is an agent skill from jellydn/my-ai-tools. Build an interactive report or experiment when the user asks to explore model capabilities.
Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: cline, claude, opencode, amp, codex, gemini, cursor, pi
It sits in Education, covering Quizzes and assessments. The repository describes itself as: Comprehensive configuration management for AI coding tools - Replicate my complete setup for Claude Code, OpenCode, Amp, Li, Codex and Claude Code Switch with custom… The licence is MIT.
3 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 163951e. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are html and markdown).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
cline, claude, opencode, amp, codex, gemini, cursor, pi
From compatibility in the SKILL.md frontmatter.
Capability Experiments loads about 2k tokens when it runs. Until then it costs about 29 tokens; SKILL.md has 393 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from jellydn/my-ai-tools at commit 163951e, republished under its MIT licence (© jellydn). 393 words, ~2,046 tokens.
.claude/skills/capability-experiments/SKILL.md (or your agent's skills folder).Use this skill when:
Teaches techniques for leveraging advanced model capabilities — HTML generation, embedded interactive elements, proactive research, and multi-step reasoning. These patterns showcase what's newly possible with next-generation models and should be used freely.
Advanced models can generate rich, self-contained HTML. This is useful for:
Generate structured HTML reports for complex findings:
<!DOCTYPE html>
<html>
<head><style>
body { font-family: system-ui; max-width: 800px; margin: 2rem auto; }
.finding { border-left: 4px solid #e74c3c; padding: 1rem; margin: 1rem 0; }
.finding.fixed { border-color: #2ecc71; }
.severity { font-weight: 600; font-size: 0.85rem; }
</style></head>
<body>
<h1>Code Review: PR #288</h1>
<div class="finding">
<span class="severity">🔴 Critical</span>
<p>Hardcoded path in config...</p>
</div>
...
</body></html>Use HTML reports when:
Generate HTML questionnaires for spec interviews and quizzes:
<form id="quiz">
<div class="question">
<p>1. Why did we choose GitHub App Installation flow?</p>
<label><input type="radio" name="q1" value="a"> OAuth is deprecated</label>
<label><input type="radio" name="q1" value="b"> Org-level access ✓</label>
</div>
<button type="button" onclick="checkAnswers()">Check</button>
</form>
<script>
function checkAnswers() {
const correct = { q1: 'b', q2: 'c' };
// ... scoring logic
}
</script>These work well with Fable's ability to render and execute embedded HTML in responses.
Use HTML/CSS to visualize decision processes:
<div class="decision-tree">
<div class="node root">Feature Change</div>
<div class="branch">
<div class="node">Familiar code?</div>
<div class="yes">→ Standard pattern</div>
<div class="no">→ /blindspots first</div>
</div>
</div>
<style>
.decision-tree { font-family: monospace; }
.node { background: #f0f0f0; padding: 8px; margin: 4px; }
.yes { color: #2ecc71; }
.no { color: #e74c3c; }
</style>Let the agent self-direct exploration rather than waiting for instructions:
Instead of asking the user what to look at, proactively scan the codebase:
1. Scan recent changes with `fff` and `git log`
2. Identify areas of concern or interest
3. Analyze patterns and potential issues
4. Report findings with actionable recommendationsBefore starting work, proactively look for gotchas:
1. Search git history for past bugs in related areas
2. Check qmd for relevant learnings
3. Search ctx for past agent discussions
4. Review existing ADRs for architectural context
5. Report findings before proposing implementationWhen faced with a complex task, probe what's possible:
1. Generate multiple approaches (not just the obvious one)
2. For each approach, assess feasibility
3. Consider approaches that were hard with older models
4. Recommend the best approach with rationaleBreak complex decisions into structured analysis:
## Analysis: Authentication Strategy
### Dimensions to Consider
1. Security requirements (OAuth 2.0, org-level access)
2. User experience (login flow, token management)
3. Maintenance (token refresh, error handling)
4. Scalability (multiple orgs, rate limits)
### Trade-offs
| Approach | Security | UX | Maintenance | Scalability |
|----------|----------|----|-------------|-------------|
| OAuth App | Medium | High | Low | Low |
| GitHub App | High | Medium | Medium | High |
| PAT | Low | Low | High | Medium |For each promising approach, gather evidence:
## Research: GitHub App Installation
### Findings
- ✓ Org-level repo access (required)
- ✓ Webhook-based events
- ✓ Token caching supported
- ✗ More complex setup
- ✗ Requires webhook endpoint
### Past Context
- Previous PR #123 attempted similar approach
- ADR-005 discusses webhook infrastructure
- qmd has learnings about token caching## Recommendation
**Approach**: GitHub App Installation Flow
**Rationale**:
1. Required for org-level access (blocker for OAuth App)
2. Token caching addresses UX concerns
3. Existing webhook infrastructure from PR #123
4. ADR-005 confirms architectural fit
**Risks**:
- Webhook endpoint needs high availability
- Token refresh handling adds complexityInteractive questionnaires improve spec interviews and knowledge verification:
Generate structured questions with HTML forms:
<h3>Architecture Questions</h3>
<div class="question">
<p><strong>Q1:</strong> Should we use a single shared database or per-tenant databases?</p>
<details>
<summary>Context</summary>
<p>Current system uses shared DB. Per-tenant improves isolation but adds operational complexity.</p>
</details>
<textarea rows="2" placeholder="Your thinking..."></textarea>
</div>Generate self-assessment quizzes:
<h3>Implementation Quiz</h3>
<form id="quiz">
<div class="q">
<p>1. What caching strategy did we use for installation tokens?</p>
<label><input type="radio" name="q1" value="r"> Redis with TTL</label>
<label><input type="radio" name="q1" value="w"> In-memory cache</label>
</div>
<button type="button" onclick="grade()">Check Understanding</button>
</form>When to Use Each Pattern:
┌──────────────────────────────┬──────────────────────────┐
│ Situation │ Use Pattern │
├──────────────────────────────┼──────────────────────────┤
│ Complex analysis to present │ HTML report │
│ Spec is vague │ Embedded questionnaire │
│ Large, unfamiliar codebase │ Proactive research scan │
│ Hard architectural decision │ Multi-step reasoning │
│ After implementation │ Embedded quiz │
│ Exploring options │ Capability probe │
└──────────────────────────────┴──────────────────────────┘© jellydn, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/capability-experiments of jellydn/my-ai-tools.
Open the folder on GitHubat commit 163951e
Capability Experiments next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Capability Experiments this skilljellydn/my-ai-tools | 123 | — | ~2k | Automated safety check: Pass | MIT | |
| DeepTutor CLIHKUDS/DeepTutor | 41k | — | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| AI Engineering Placement Quizrohitg00/ai-engineering-from-scratch | 65k | — | ~2k | Automated safety check: Pass | MIT | |
| Codebase to Coursezarazhangrui/codebase-to-course | 5.7k | — | ~4.4k | Automated safety check: Pass | None | |
| AI Engineering Phase Quizrohitg00/ai-engineering-from-scratch | 65k | — | ~2.1k | Automated safety check: Pass | MIT | |
| Scholar EvaluationK-Dense-AI/claude-scientific-writer | 2.4k | 2 repos | ~2.9k | Automated safety check: Notes | MIT |
HKUDS/DeepTutor
Teaches the agent to set up and run DeepTutor from the command line: chat and capabilities, knowledge bases, partners, memory, sessions, notebooks and the server or Web app.
rohitg00/ai-engineering-from-scratch
Runs a 10-question quiz across five areas to place a learner in the AI Engineering from Scratch curriculum, so they skip what they already know.
zarazhangrui/codebase-to-course
Turns a codebase into an interactive single-page HTML course for non-technical learners, with scroll modules, animated diagrams, quizzes and plain-English code translations.
rohitg00/ai-engineering-from-scratch
Quizzes you on a completed phase of the AI Engineering from Scratch course, taking a phase number or name and mapping it to that phase's directory.
K-Dense-AI/claude-scientific-writer
Provide qualitative-first, evidence-traceable developmental review of scholarly works and audit low-stakes research-assessment rubrics with optional local quality controls.
guanyang/open-agent-hub
This skill should be used when building agent evaluation systems: deterministic checks, regression suites, multi-dimensional rubrics, quality gates, production monitoring, baseline comparison, and…
jellydn/my-ai-tools
A skill your agent uses when monitoring an open GitHub PR for CI failures, review feedback, mergeability, and safe retries or fixes.
jellydn/my-ai-tools
Posts a concise visual outline as a GitHub pull request comment.
jellydn/my-ai-tools
Manage project knowledge with qmd — captures learnings, decisions, and conventions
jellydn/my-ai-tools
Generate Product Requirements Documents from feature ideas — plans specs and requirements
jellydn/my-ai-tools
Fix PR review comments by implementing requested changes. An agent skill from jellydn/my-ai-tools.
jellydn/my-ai-tools
Convert PRDs to prd.json format for the Ralph autonomous agent system
Categories
Build an interactive report or experiment when the user asks to explore model capabilities. Capability Experiments is an agent skill from jellydn/my-ai-tools. Build an interactive report or experiment when the user asks to explore model capabilities.
Capability Experiments fits situations like: asks to explore model capabilities; tasks that involve Quizzes and assessments.
Run `npx skills add jellydn/my-ai-tools --skill capability-experiments -a claude-code`. Or copy the skill folder (skills/capability-experiments in jellydn/my-ai-tools) into .claude/skills/capability-experiments in your project. Claude Code loads it when a task matches its description.
Run `npx skills add jellydn/my-ai-tools --skill capability-experiments -a codex`. Or copy the skill folder (skills/capability-experiments in jellydn/my-ai-tools) into .agents/skills/capability-experiments in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jellydn/my-ai-tools --skill capability-experiments -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/capability-experiments, .gemini/skills/capability-experiments, .github/skills/capability-experiments and .opencode/skills/capability-experiments in your project.
SKILL.md names no scripts, command-line tools or credentials: Capability Experiments is instructions for the agent only. Compatibility (from SKILL.md): cline, claude, opencode, amp, codex, gemini, cursor, pi.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Capability Experiments is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 2k tokens (SKILL.md is roughly 8.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Capability Experiments: DeepTutor CLI (HKUDS/DeepTutor, 41k stars), AI Engineering Placement Quiz (rohitg00/ai-engineering-from-scratch, 65k stars), Codebase to Course (zarazhangrui/codebase-to-course, 5.7k stars) and AI Engineering Phase Quiz (rohitg00/ai-engineering-from-scratch, 65k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
jellydn (a GitHub user) maintains it in jellydn/my-ai-tools, which has 123 GitHub stars. The repository holds 35 skills in this directory. The repository was last updated on October 7, 2026.
Source: jellydn/my-ai-tools on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.