@xl0/pi-lovely-agents 0.1.0

package/package.json

@@ -0,0 +1,68 @@
+{
+	"name": "@xl0/pi-lovely-agents",
+	"version": "0.1.0",
+	"description": "Agent orchestration for Pi",
+	"keywords": [
+		"pi-package",
+		"agents"
+	],
+	"type": "module",
+	"publisher": "xl0",
+	"author": {
+		"name": "xl0",
+		"url": "https://github.com/xl0"
+	},
+	"license": "MIT",
+	"homepage": "https://github.com/xl0/pi-lovely-agents#readme",
+	"bugs": {
+		"url": "https://github.com/xl0/pi-lovely-agents/issues"
+	},
+	"repository": {
+		"type": "git",
+		"url": "git+https://github.com/xl0/pi-lovely-agents.git"
+	},
+	"packageManager": "bun@1.3.13",
+	"files": [
+		"extensions/",
+		"skills/",
+		"README.md",
+		"CHANGELOG.md",
+		"LICENSE"
+	],
+	"scripts": {
+		"test": "bun test",
+		"typecheck": "tsgo --noEmit",
+		"check": "bun run typecheck && bun run test && bun run biome:check",
+		"prepublishOnly": "bun run check",
+		"release": "bun run scripts/release.ts",
+		"lint": "biome lint .",
+		"format": "biome format --write .",
+		"format:check": "biome format .",
+		"biome:check": "biome check ."
+	},
+	"devDependencies": {
+		"@biomejs/biome": "^2.4.14",
+		"@typescript/native-preview": "^7.0.0-dev.20260502.1",
+		"bun-types": "^1.3.13",
+		"typescript": "^6.0.3"
+	},
+	"peerDependencies": {
+		"@earendil-works/pi-coding-agent": "*",
+		"@earendil-works/pi-tui": "*",
+		"typebox": "*"
+	},
+	"pi": {
+		"extensions": [
+			"./extensions"
+		],
+		"skills": [
+			"./skills"
+		]
+	},
+	"dependencies": {
+		"@xl0/pi-lovely-config": "^0.1.3"
+	},
+	"bundledDependencies": [
+		"@xl0/pi-lovely-config"
+	]
+}

package/skills/agent/SKILL.md

@@ -0,0 +1,21 @@
+---
+name: agent
+description: Use when deciding whether and how to delegate work to subagents.
+---
+
+# Delegation
+
+Delegate to reduce total work, not to maximize parallelism.
+
+- Best fit: research, exploration, API/doc lookup, and independent review.
+- Coding fits when isolated: bounded files, stable interfaces, independently
+  testable output. Unless it's a clear win, prefer to do the coding yourself.
+- Keep architecture, shared types, and integration with the parent. Splitting
+  coupled code often costs more coordination and review than it saves.
+- Give the goal, relevant context, constraints, ownership, and acceptance criteria.
+  Request findings with evidence or changes with test results—not transcripts.
+- Parallelize independent questions or modules. Keep useful work for yourself;
+  don't duplicate the delegate's task.
+- Verify findings and integrate changes. Delegation transfers work, not responsibility.
+
+If briefing, waiting, and integration outweigh doing it yourself, don't delegate.

package/skills/agent-creator/SKILL.md

@@ -0,0 +1,35 @@
+---
+name: agent-creator
+description: Create or edit Lovely Agents definitions when the user wants a reusable agent role.
+---
+
+# Create an agent definition
+
+- Call `agent_roster` first. Reuse or edit an existing role when it fits;
+  don't silently overwrite or shadow one.
+- Default to the project's active `.pi/agents/` directory (nearest ancestor).
+  Create one if absent. Use `~/.pi/agent/agents/` for explicitly user-wide roles.
+  Save as `<name>.md`.
+- Start with YAML between `---` lines. These are the only allowed fields:
+  - `name` (required): match `[a-z0-9][a-z0-9_-]{0,63}`; unique within its scope.
+  - `description` (required): nonblank, at most 500 UTF-8 bytes.
+  - `model`: `provider/model-id`, an unambiguous model ID, or a configured
+    `fast`/`smart`/`workhorse` alias. Omitted → starting session's model.
+  - `thinking`: `off`, `minimal`, `low`, `medium`, `high`, `xhigh`, or `max`.
+    Omitted → alias preset, otherwise starting session's level. Pi clamps
+    unsupported levels.
+  - `tools`: YAML list or comma-separated names, without duplicates. Omitted →
+    normal tools/extensions; `[]` → no tools.
+  - `exclude_agents_md`: boolean, default `false`. `true` omits discovered
+    `AGENTS.md`/`CLAUDE.md` instructions.
+- Make the description explain when to choose this agent. A nonempty Markdown
+  body after the closing `---` is required. Keep it concise:
+  purpose, boundaries, what to inspect or change, and expected results.
+  Keep one-off assignments out of the reusable definition.
+- Use known tool names and an explicit allowlist when restricting the role.
+  Bash access is not read-only. Keep AGENTS/CLAUDE instructions enabled unless
+  the user asks otherwise.
+- Leave model/thinking inherited unless requested. If selecting them, verify
+  the model or enabled alias rather than inventing an ID.
+- Call `agent_roster` again and fix diagnostics for the edited definition.
+  Report its path and role. Don't launch an agent merely to test the definition.