list_skill

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.