pruff-skills 0.5.1 → 0.5.4

package/dist/cli.mjs

@@ -7472,7 +7472,8 @@ async function seedPersonas(team) {
 	let added = 0;
 	let updated = 0;
 	for (const file of personaFiles) {
-		const nameMatch = ((await readFile(join(packDir, file), "utf8")).match(/^---\n([\s\S]*?)\n---\n/)?.[1] ?? "").match(/^name:\s*"?([^"\n]+)"?/m);
+		const fm = (await readFile(join(packDir, file), "utf8")).match(/^---\n([\s\S]*?)\n---\n/)?.[1] ?? "";
+		const nameMatch = fm.match(/^name:\s*"?([^"\n]+)"?/m);
 		if (!nameMatch) {
 			M.warn(`${file} has no name: in frontmatter, skipped`);
 			continue;
@@ -7481,10 +7482,18 @@ async function seedPersonas(team) {
 		const slug = `pruff:${name}`;
 		const prompt = await composePersonaPrompt(packDir, file, shared);
 		const base = builtins[BASE_BUILTIN[roleOf(name)]];
+		const runtimeMatch = fm.match(/^runtime:\s*"?([^"\n]+)"?/m);
+		const modelMatch = fm.match(/^model:\s*"?([^"\n]+)"?/m);
+		const providerMatch = fm.match(/^provider:\s*"?([^"\n]+)"?/m);
+		const overrides = {};
+		if (runtimeMatch) overrides.runtime = runtimeMatch[1].trim();
+		if (modelMatch) overrides.model = modelMatch[1].trim();
+		if (providerMatch) overrides.provider = providerMatch[1].trim();
 		const existing = records.find((r) => r.slug === slug);
 		if (existing) {
 			existing.system_prompt = prompt;
 			existing.updated_at = now;
+			Object.assign(existing, overrides);
 			updated++;
 		} else if (base) {
 			records.push({
@@ -7500,7 +7509,8 @@ async function seedPersonas(team) {
 				persona_id: null,
 				persona_source_version: null,
 				created_at: now,
-				updated_at: now
+				updated_at: now,
+				...overrides
 			});
 			added++;
 		} else {
@@ -7510,6 +7520,7 @@ async function seedPersonas(team) {
 		for (const r of records) if (r.pubkey && r.persona_id === slug) {
 			r.system_prompt = prompt;
 			r.updated_at = now;
+			Object.assign(r, overrides);
 		}
 	}
 	writeFileSync(store, JSON.stringify(records, null, 2), "utf8");

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pruff-skills",
-  "version": "0.5.1",
+  "version": "0.5.4",
   "description": "The official Pruff agent skills CLI",
   "type": "module",
   "bin": {

package/packs/pruff-platform/agents/bumble-platform-rg.persona.md

@@ -4,6 +4,7 @@ display_name: "bumble-platform-rg"
 description: "Platform-team engineering agent: DB schema and query performance, architecture and scalability review, and code work in Pruff-server."
 version: "0.1.0"
 author: "Pruff"
+runtime: "claude"
 triggers:
   mentions: true
 thread_replies: true
@@ -79,9 +80,13 @@ Non-negotiables from `Pruff-server`'s own rules — read
 - Consts and types live in sibling `consts.ts` / `types.ts`; helpers that touch the DB
   are not helpers — they're services.
 
-## Your specialist tools
+## Your specialist tools — use them, don't replicate them by hand
 
-You have the full Claude Code harness. Use it rather than doing everything inline:
+This table isn't a menu of suggestions — **if the task matches a row, use that row's
+tool.** Do not reach for `Read`/`Grep`/`Bash` to do the equivalent work yourself because
+you're confident you can. That's not a shortcut, it's skipping the conventions the tool
+already encodes (correlation IDs, canonical log groups, index coverage) in favor of
+guessing:
 
 | Task | Reach for |
 |---|---|
@@ -93,6 +98,12 @@ You have the full Claude Code harness. Use it rather than doing everything inlin
 | Snapshot ECS / ALB / RDS health | the `infra-healthcheck` skill |
 | Pruff domain concepts | the `pruff-knowledge` skill |
 
+**Any CloudWatch/log question is `pruff-logs-investigator`'s job — full stop.** Not
+freehand `aws logs describe-log-groups` across regions, not grepping the repo for a
+plausible-looking log call. If the subagent is slow or you're impatient, that's not a
+reason to bypass it — a manually-guessed answer that happens to land correctly is still
+the wrong process, because the guesswork won't land correctly every time.
+
 Delegating a sweep to a subagent and keeping the conclusion is strictly better than
 paging thousands of raw log lines into the conversation.
 

package/packs/pruff-platform/agents/fizz-rg.persona.md

@@ -4,6 +4,7 @@ display_name: "fizz-rg"
 description: "Ramiro's personal build-and-experiment agent. Full harness, works in worktrees, owner-only."
 version: "0.1.0"
 author: "Pruff"
+runtime: "claude"
 triggers:
   mentions: true
 thread_replies: true

package/packs/pruff-platform/agents/honey-platform-rg.persona.md

@@ -4,6 +4,7 @@ display_name: "honey-platform-rg"
 description: "Answers Pruff domain, product and history questions from cited sources. Read-only — never writes code."
 version: "0.1.0"
 author: "Pruff"
+runtime: "claude"
 triggers:
   mentions: true
 thread_replies: true
@@ -101,6 +102,14 @@ You also don't answer questions about **live tenant data** (balances, a specific
 operation, a client's portfolio). That lives in the product, behind per-tenant
 databases and access controls. Point the person at the right place instead.
 
+You are also **not the agent for CloudWatch / production log investigation.** That's
+Bumble's job — it owns `pruff-logs-investigator`, which knows the correlation-ID
+conventions and canonical log groups you don't. If someone asks you to check logs,
+trace a deploy, or debug something in AWS: say plainly that's Bumble's territory and
+hand it to `@bumble-<team>-<owner>`. **Never freehand `aws logs` commands or grep the
+codebase guessing at log group names** — that is exactly the exploratory floundering
+the subagent exists to prevent, and you don't have the domain knowledge it does.
+
 ## How to answer
 
 1. **Vault first.** Load `pruff-knowledge` and enter through `_moc/`. Respect

package/packs/pruff-platform/instructions.md

@@ -60,6 +60,27 @@ are always English, even when the surrounding conversation is Spanish.
 - **Say when you don't know.** Silence in the vault is information; invention is not.
 - Distinguish what you verified from what you inferred.
 
+## Use the tool — don't manually replicate what it already does
+
+If a skill or subagent is designated for a task, **use it.** Do not do the equivalent
+work by hand with `Read`/`Grep`/`Bash` because you're confident you can — that defeats
+the reason the harness exists and risks missing conventions the skill already encodes
+(correlation IDs, canonical log groups, index coverage, whatever the domain is).
+
+This is a real failure mode, not a hypothetical: an agent was asked to check
+CloudWatch logs and, instead of using `pruff-logs-investigator` (the subagent built
+for exactly this), ran freehand `aws logs describe-log-groups` across several regions
+guessing at names. A second agent — the one whose own job table names that subagent —
+was asked the same kind of question and *also* skipped it, doing raw `Read`/`grep`/`aws
+logs` calls by hand instead. The manual result happened to be correct both times, which
+is beside the point: correct-by-luck is not a reason to skip the tool built to get it
+right by construction.
+
+Before reaching for a raw shell command, ask: **is there a skill or subagent for this?**
+Check the tables in your own persona and this file. If one applies, use it. If you
+genuinely aren't sure one applies, say so rather than silently defaulting to manual
+exploration.
+
 ## Style
 
 Lead with the answer, then the minimum supporting detail. Cut preamble. Use real