Run any Skill in Manus with one click

inspect-trail

Stars0

Forks0

UpdatedMay 22, 2026 at 03:14

Shows detailed progress and status for a specific trail in an EstudeMe vault: modules covered, notes per module, completion percentage. Use when the user asks 'how is my trail X', 'status of trail X', 'progress on the Java trail'. Don't use to list multiple trails — use list-trails.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

josenaldo

josenaldo/estudeme

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	inspect-trail
description	Shows detailed progress and status for a specific trail in an EstudeMe vault: modules covered, notes per module, completion percentage. Use when the user asks 'how is my trail X', 'status of trail X', 'progress on the Java trail'. Don't use to list multiple trails — use list-trails.
license	MIT
compatibility	claude-code, gemini-cli, copilot, codex

Skill: Inspect Trail

Instructions

Step 1: Gather inputs

Confirm two pieces of information with the user: the vault path and the trail title (the value of the title field in the trail's frontmatter).
If the user mentions the trail without a title (e.g., "my Java trail"), run estudeme trail list <vault> first to find the exact title.

Step 2: Run the CLI

Execute: estudeme trail status <vault-path> "<trail-title>"
Quote the trail title — it likely contains spaces.

Step 3: Report back

On success: present the progress summary (modules completed, total notes, percent done) plus any next-step suggestions the CLI emits.
On failure: surface the error and propose a fix (e.g., trail not found → check title spelling via list-trails).

Critical

Read-only skill. Never run commands that write to the vault.
Always quote the trail title in the CLI call.

Examples

Example 1: Direct status

User says: "How is my Java Backend trail going in ~/study/my-vault?"

Actions:

Run estudeme trail status ~/study/my-vault "Java Backend"
Receive the progress data
Present completion percentage, modules done, and notes count

Result: User sees a clear progress summary.

Example 2: Title disambiguation

User says: "Show me my Kubernetes progress" (vault path known, title approximate).

Actions:

Run estudeme trail list <vault> to find the exact title
Confirm the match with the user if multiple candidates exist
Run estudeme trail status <vault> "<exact-title>"

Result: Status shown for the right trail, no ambiguity.

Troubleshooting

Error: Trail not found

Cause: title misspelled or trail does not exist.
Solution: run estudeme trail list <vault> to see the available titles and re-run with the correct one.

Error: Cannot find vault directory

Cause: bad vault path.
Solution: confirm with the user; verify with ls.

Performance Notes

One CLI call per trail. Do not loop to "discover" trails — use list-trails for that and pass the exact title back here.

More from this repository

same repository

export-cards

josenaldo/estudeme

Exports flashcards from an EstudeMe vault into a neutral JSON file (suitable for Anki import). Use when the user asks 'export my cards', 'export cards to Anki', 'give me a card export', or wants to take cards out of the vault. Don't use to list cards in place — use list-cards.

2026-05-240

review-vault-state

josenaldo/estudeme

Gives a complete state overview of an EstudeMe vault by orchestrating validation, trail listing, and metrics into a single coherent report. Use when the user asks 'how is my vault', 'give me an overview', 'state of my study system', 'review my vault'. Don't use for a single trail — use inspect-trail.

2026-05-240

list-trails

josenaldo/estudeme

A test skill that should be ignored by the vault parser.

2026-05-230

report-metrics

josenaldo/estudeme

Reports vault-wide metrics in an EstudeMe vault: trail count, module count, notes per trail, cards per trail, overall structure summary. Use when the user asks 'show vault metrics', 'how is my progress overall', 'give me numbers on my vault'. Don't use to inspect a single trail — use inspect-trail.

2026-05-220

validate-vault

josenaldo/estudeme

Validates an EstudeMe vault: checks frontmatter against the schema for each document type and reports broken wikilinks. Use when the user asks 'validate my vault', 'check my vault', 'any broken links', 'is my vault healthy'. Don't use to inspect a specific trail's progress — use inspect-trail.

2026-05-220

list-cards

josenaldo/estudeme

Lists all flashcards in an EstudeMe vault. Use when the user asks 'list my cards', 'what flashcards do I have', 'show me my cards', or wants a card inventory. Don't use to export cards to an external format — use export-cards.

2026-05-220

name	inspect-trail
description	Shows detailed progress and status for a specific trail in an EstudeMe vault: modules covered, notes per module, completion percentage. Use when the user asks 'how is my trail X', 'status of trail X', 'progress on the Java trail'. Don't use to list multiple trails — use list-trails.
license	MIT
compatibility	claude-code, gemini-cli, copilot, codex

Skill: Inspect Trail

Instructions

Step 1: Gather inputs

Confirm two pieces of information with the user: the vault path and the trail title (the value of the title field in the trail's frontmatter).
If the user mentions the trail without a title (e.g., "my Java trail"), run estudeme trail list <vault> first to find the exact title.

Step 2: Run the CLI

Execute: estudeme trail status <vault-path> "<trail-title>"
Quote the trail title — it likely contains spaces.

Step 3: Report back

On success: present the progress summary (modules completed, total notes, percent done) plus any next-step suggestions the CLI emits.
On failure: surface the error and propose a fix (e.g., trail not found → check title spelling via list-trails).

Critical

Read-only skill. Never run commands that write to the vault.
Always quote the trail title in the CLI call.

Examples

Example 1: Direct status

User says: "How is my Java Backend trail going in ~/study/my-vault?"

Actions:

Run estudeme trail status ~/study/my-vault "Java Backend"
Receive the progress data
Present completion percentage, modules done, and notes count

Result: User sees a clear progress summary.

Example 2: Title disambiguation

User says: "Show me my Kubernetes progress" (vault path known, title approximate).

Actions:

Run estudeme trail list <vault> to find the exact title
Confirm the match with the user if multiple candidates exist
Run estudeme trail status <vault> "<exact-title>"

Result: Status shown for the right trail, no ambiguity.

Troubleshooting

Error: Trail not found

Cause: title misspelled or trail does not exist.
Solution: run estudeme trail list <vault> to see the available titles and re-run with the correct one.

Error: Cannot find vault directory

Cause: bad vault path.
Solution: confirm with the user; verify with ls.

Performance Notes

One CLI call per trail. Do not loop to "discover" trails — use list-trails for that and pass the exact title back here.