Run any Skill in Manus with one click

list-trails

Stars0

Forks0

UpdatedMay 22, 2026 at 03:14

Lists all trails (learning tracks) in an EstudeMe vault. Use when the user asks 'what trails do I have', 'list my trails', 'show me my trails', or wants an overview of their learning tracks. Don't use for progress detail on a specific trail — use inspect-trail.

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	list-trails
description	Lists all trails (learning tracks) in an EstudeMe vault. Use when the user asks 'what trails do I have', 'list my trails', 'show me my trails', or wants an overview of their learning tracks. Don't use for progress detail on a specific trail — use inspect-trail.
license	MIT
compatibility	claude-code, gemini-cli, copilot, codex

Skill: List Trails

Instructions

Step 1: Confirm the vault path

If the user has not stated the vault path, ask for it. The vault is a directory of Markdown notes with EstudeMe frontmatter.
Verify the directory exists. If not, surface the error and stop.

Step 2: Run the CLI

Execute: estudeme trail list <vault-path>
Capture stdout and the exit code.

Step 3: Report back

On success (exit 0): present each trail with its title, level, and status. Keep the output compact.
On failure: surface the error and suggest estudeme validate <vault-path> to diagnose.

Critical

This skill is read-only. Never invoke any command that writes to the vault.
Never assume the vault path. Always confirm it with the user.

Examples

Example 1: Direct listing

User says: "What trails do I have in ~/study/my-vault?"

Actions:

Run estudeme trail list ~/study/my-vault
Receive the trail list
Present each trail with level and status

Result: User sees the full list of trails.

Example 2: Missing path

User says: "List my trails."

Actions:

Ask: "Which vault directory should I list trails from?"
Wait for the user to provide a path before proceeding.

Result: User specifies the path; skill proceeds as in Example 1.

Troubleshooting

Error: Cannot find vault directory

Cause: the path does not exist or is not a directory.
Solution: confirm the path spelling with the user; verify it with ls.

Error: No trails found in vault

Cause: the vault has no Markdown files with type: trail in frontmatter.
Solution: the user may not have created trails yet (suggest estudeme init), or trails are present but malformed (suggest estudeme validate <vault>).

Performance Notes

Always pass the full vault path. The CLI does not auto-discover the vault.

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	list-trails
description	Lists all trails (learning tracks) in an EstudeMe vault. Use when the user asks 'what trails do I have', 'list my trails', 'show me my trails', or wants an overview of their learning tracks. Don't use for progress detail on a specific trail — use inspect-trail.
license	MIT
compatibility	claude-code, gemini-cli, copilot, codex

Skill: List Trails

Instructions

Step 1: Confirm the vault path

If the user has not stated the vault path, ask for it. The vault is a directory of Markdown notes with EstudeMe frontmatter.
Verify the directory exists. If not, surface the error and stop.

Step 2: Run the CLI

Execute: estudeme trail list <vault-path>
Capture stdout and the exit code.

Step 3: Report back

On success (exit 0): present each trail with its title, level, and status. Keep the output compact.
On failure: surface the error and suggest estudeme validate <vault-path> to diagnose.

Critical

This skill is read-only. Never invoke any command that writes to the vault.
Never assume the vault path. Always confirm it with the user.

Examples

Example 1: Direct listing

User says: "What trails do I have in ~/study/my-vault?"

Actions:

Run estudeme trail list ~/study/my-vault
Receive the trail list
Present each trail with level and status

Result: User sees the full list of trails.

Example 2: Missing path

User says: "List my trails."

Actions:

Ask: "Which vault directory should I list trails from?"
Wait for the user to provide a path before proceeding.

Result: User specifies the path; skill proceeds as in Example 1.

Troubleshooting

Error: Cannot find vault directory

Cause: the path does not exist or is not a directory.
Solution: confirm the path spelling with the user; verify it with ls.

Error: No trails found in vault

Cause: the vault has no Markdown files with type: trail in frontmatter.
Solution: the user may not have created trails yet (suggest estudeme init), or trails are present but malformed (suggest estudeme validate <vault>).

Performance Notes

Always pass the full vault path. The CLI does not auto-discover the vault.