@action-llama/skill 0.23.8 → 0.24.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,3 +1,9 @@
1
+ ---
2
+ name: debug
3
+ description: Diagnose why an Action Llama agent is failing and suggest fixes. Use when debugging, troubleshooting, or investigating agent errors.
4
+ argument-hint: "[agent-name]"
5
+ ---
6
+
1
7
  # Debug a failing agent
2
8
 
3
9
  Diagnose why an agent is failing and suggest fixes.
@@ -10,16 +16,19 @@ Diagnose why an agent is failing and suggest fixes.
10
16
 
11
17
  3. Call `al_agents` with the agent name to read its full config and SKILL.md body.
12
18
 
13
- 4. Analyze the logs and agent configuration to identify the root cause. Common issues:
19
+ 4. For detailed reference on agent commands, exit codes, and runtime context, read `debugging.md` from the `al` skill.
20
+
21
+ 5. Analyze the logs and agent configuration to identify the root cause. Common issues:
14
22
  - Missing or expired credentials
15
23
  - Malformed SKILL.md frontmatter
16
24
  - Instructions that lead to tool errors
17
25
  - Rate limiting or API failures
18
26
  - Docker/container issues
27
+ - Resource lock contention
19
28
 
20
- 5. Present a diagnosis with:
29
+ 6. Present a diagnosis with:
21
30
  - **Root cause**: What's going wrong and why
22
31
  - **Evidence**: Relevant log lines
23
32
  - **Fix**: Concrete changes to make (SKILL.md edits, credential updates, config changes)
24
33
 
25
- 6. Offer to apply the fix directly.
34
+ 7. Offer to apply the fix directly.
@@ -1,3 +1,9 @@
1
+ ---
2
+ name: iterate
3
+ description: Run an Action Llama agent, analyze output, and improve its instructions. Repeats up to 3 cycles. Use when iterating on, improving, or refining an agent.
4
+ argument-hint: "[agent-name]"
5
+ ---
6
+
1
7
  # Iterate on an agent
2
8
 
3
9
  Run an agent, analyze its output, and improve its instructions. Repeats up to 3 cycles or until the agent runs cleanly.
@@ -0,0 +1,36 @@
1
+ ---
2
+ name: new-agent
3
+ description: Create a new Action Llama agent with SKILL.md and config.toml. Use when creating, adding, or scaffolding a new agent.
4
+ argument-hint: "<agent-name>"
5
+ ---
6
+
7
+ # Create a new agent
8
+
9
+ Create a new Action Llama agent named `$ARGUMENTS`.
10
+
11
+ ## Steps
12
+
13
+ 1. Ask the user for:
14
+ - **Trigger type**: `schedule` (cron), `webhook`, or both
15
+ - If schedule: a cron expression (e.g. `*/5 * * * *`)
16
+ - If webhook: the provider and event (e.g. `github` / `issues.opened`)
17
+ - **Credentials** needed (e.g. `github_token`, `slack_bot_token`)
18
+ - A one-sentence description of what the agent should do
19
+
20
+ 2. Use `al_agents` to list existing agents and avoid name conflicts.
21
+
22
+ 3. Create `agents/$ARGUMENTS/SKILL.md` with:
23
+ - YAML frontmatter containing portable metadata only: `name`, `description`, optionally `license` and `compatibility`
24
+ - Do NOT include `name` or `model` in the frontmatter — name is derived from the directory, model is inherited from project config
25
+ - A markdown body with clear instructions for the agent
26
+ - For the full SKILL.md specification and available agent commands, read `agent-authoring.md` from the `al` skill
27
+
28
+ 4. Create `agents/$ARGUMENTS/config.toml` with runtime configuration:
29
+ - `models` — list of named model references from project `config.toml`
30
+ - `credentials` — list of credential types the agent needs
31
+ - `schedule` and/or `webhooks` — trigger configuration
32
+ - For the full config.toml reference, read `agent-authoring.md` from the `al` skill
33
+
34
+ 5. Confirm the agent was created and suggest next steps:
35
+ - `al doctor` to verify credentials
36
+ - `/al:run` to test it
@@ -1,3 +1,9 @@
1
+ ---
2
+ name: run
3
+ description: Trigger an Action Llama agent run and report the results. Use when running, triggering, or testing an agent.
4
+ argument-hint: "[agent-name]"
5
+ ---
6
+
1
7
  # Run an agent
2
8
 
3
9
  Trigger an agent run and report the results.
@@ -1,3 +1,8 @@
1
+ ---
2
+ name: status
3
+ description: Show a rich overview of the Action Llama project status including scheduler state and agent details. Use when checking status, health, or state of the project.
4
+ ---
5
+
1
6
  # Status overview
2
7
 
3
8
  Show a rich overview of the Action Llama project status.