list-skill

name	list_skill
description	List all available ACLIx skills by executing a python directory scanner.

Purpose

Deliver a single, authoritative inventory of filesystem-based ACLIx skills (directories that contain a SKILL.md entrypoint). Prefer the bundled python scanner; if that path is unavailable, continue automatically via a constrained shell fallback—never stop at “Python missing” without producing a table for the user.

Standard Operating Procedure

Trigger

Activate this procedure whenever the user asks to list skills, show available skills, enumerate skills, or any equivalent inventory request.

---

1. Primary method (Python engine)

1. Read the injected anchor at the very top of the skill payload returned by read_skill. Extract the absolute path from the line:

   • [Skill Directory: <absolute_path>]
   • Hereafter, call this value INJECTED_SKILL_DIR (it is the directory that contains this skill’s SKILL.md).

2. Invoke the python tool with:

   • scriptPath: INJECTED_SKILL_DIR + /scripts/scanner.py (no trailing slash issues; normalize mentally to a single absolute path).
   • code: omit.
   • args: omit for the default behavior (scanner walks ~/.aclix/skills and ./.aclix/skills relative to the agent process cwd). If the user requests a single alternate filesystem root, pass one argument: that directory path (the script treats sys.argv[1] as the sole scan root).

3. Success path — stdout is one JSON object from json.dumps. Parse it. Expect:

   • skills: array of records with at least folder_name, skill_directory, skill_md_path, name, description (any of the metadata fields may be JSON null).

4. Failure of the primary method — Treat any of the following as failure: tool error string, non-JSON stdout, empty/corrupt JSON, or a message indicating python3 / python could not be executed. Do not apologize at length, do not ask the user whether fallback is allowed, and do not abort the task. Immediately continue to Section 2.

---

2. Fallback method (shell engine)

Condition: Use this block only when Section 1 failed.

Behavioral requirement: If the python tool fails (for example Python is not installed, the executable is not on PATH, or the process exits before emitting valid JSON), you must automatically fall back to the shell tool. Do not stop after reporting Python unavailability.

EXEMPTION: For this specific fallback step, you are EXPLICITLY GRANTED AN EXCEPTION to the global system rule that forbids using find and grep in the shell, because we are using targeted depth and constraints.

Command — copy, substitute paths, then run as one invocation:

Replace [Skill Directory] below with the same absolute path you captured as INJECTED_SKILL_DIR in Section 1.
Breadth note: That path points at this skill’s leaf folder (e.g. …/list_skill). Sibling packaged skills usually live under its parent (e.g. …/builtin-skills). To include those siblings in the fallback scan, substitute the parent directory of INJECTED_SKILL_DIR for the third search root instead of the leaf folder, when your goal is a full bundled set.

find ~/.aclix/skills ./.aclix/skills "[Skill Directory]" -maxdepth 3 -type f -name "SKILL.md" 2>/dev/null | xargs grep -H -E '^(name|description):'

shell tool parameters:

• command: the filled-in one-liner (with real paths, no bracket placeholders).
• reasoning: concise justification, e.g. “Python scanner unavailable; bounded find/grep fallback per list_skill SOP.”
• risk: low

Parsing grep output:

• Each line typically looks like <filepath>:name: <value> or <filepath>:description: <value> (the file path is everything before the first : on the line; your environment may use : in paths—if so, split only after the known .md boundary or re-read the file with file_read for ambiguous rows).
• Group lines by SKILL.md path. Pair name and description per file. Derive folder name as the basename of the directory containing that SKILL.md.

Empty input: If find produces no paths, xargs may behave oddly on some systems. If you get no usable lines, rerun with a safer pattern such as find … -exec grep -H -E '^(name|description):' {} + (still risk: low, same exemption applies).

---

3. Presentation

Unified output: Whether data came from Section 1 (JSON) or Section 2 (grep), render one professional Markdown table for the user.

Columns (in this order):

Column	Rule
Scope	Infer from each skill’s filesystem path: User if under the user’s home and includes /.aclix/skills (e.g. ~/.aclix/skills/...); Project if under the agent’s current project tree and includes /.aclix/skills (the resolved ./.aclix/skills location); Built-in if neither (e.g. packaged builtin-skills or other install-relative paths).
Name	Frontmatter name, or folder name if missing.
Description	Frontmatter description, or an em dash / short placeholder if missing.

• Escape | inside cells so the table stays valid Markdown.
• Prepend a one-line summary with the total row count.
• If there are zero skills, say so explicitly and list which roots were scanned (Python defaults, custom argv[1], or the three fallback find roots).

Fallback disclosure: If Section 2 ran, append below the table, in smaller emphasis:

(Data retrieved via shell fallback due to Python tool unavailability)

---

Notes

• Do not edit scanner.py or arbitrary skill files unless the user explicitly requests it.
• When Section 1 succeeds, omit the fallback footnote entirely.