🛠️ Update various documentation, scripts, and configuration templates to enhance clarity, functionality, and maintainability across the project

resources/skills/copilot-cost-review/SKILL.md

@@ -0,0 +1,40 @@
+---
+name: copilot-cost-review
+description: "Use when reviewing a prompt, instruction, agent, or skill draft for avoidable token cost and reuse opportunities."
+argument-hint: "target=<resource path or description>"
+---
+
+# Copilot Cost Review
+
+Use this skill when you want to make a Copilot resource cheaper to run without
+stripping away the behavior it actually needs.
+
+## Procedure
+
+1. Identify the resource's real job, expected inputs, and default output size.
+2. Search for an existing shared resource that already covers most of the same
+   workflow before proposing a new artifact.
+3. Re-evaluate the primitive choice: use an instruction for durable rules, a
+   skill for a portable workflow, a prompt for a thin VS Code entrypoint, and a
+   hook only for deterministic enforced behavior.
+4. Remove repeated policy text, long examples, and broad workspace-reading
+   requirements unless they materially improve correctness.
+5. Replace broad discovery steps with narrow anchors such as a file, symbol,
+   command, or manifest row whenever possible.
+6. Add or tighten an explicit output budget and note when the resource should
+   not be used.
+7. If the resource is still too heavy, split reference material into docs or
+   scripts and keep the runtime resource concise.
+
+## Outputs
+
+- Recommended primitive
+- Reuse candidates in the shared repo
+- Context and prompt reductions
+- Output-budget guidance
+- Non-goals or usage limits
+
+## Notes
+
+- Reduce prompt size without removing information that changes correctness.
+- Treat transcript prompt-cost fields as proxies, not exact billing data.

resources/skills/copilot-reuse-audit/SKILL.md

@@ -0,0 +1,52 @@
+---
+name: copilot-reuse-audit
+description: "Use when auditing the last 30 days of persisted Copilot artifacts for reusable patterns worth promoting into the shared repo."
+argument-hint: "days=<n> workspace=<optional path filter> sources=<optional csv>"
+---
+
+# Copilot Reuse Audit
+
+Use this skill when you want a repeatable audit of local Copilot usage artifacts
+to find patterns that should become shared resources.
+
+## Procedure
+
+1. Run `resources/scripts/audit-copilot-usage.sh` instead of manually hunting
+   through transcripts, memories, and publish logs.
+2. By default, the runner excludes the `copilot-resources` repo root from
+   workspace-backed candidate discovery so the audit does not ask you to review
+   patterns that already live in the shared repository.
+3. Review the generated `audit-summary.md` first to understand coverage and top
+   candidates.
+4. Use `selection-manifest.tsv` and `pattern-details/*.md` as the approval
+   surface for each candidate.
+5. When you want interactive triage inside Copilot, use the
+   `review-audit-candidates` prompt so each pending row is handled one at a
+   time and written back to `selection-manifest.tsv`.
+6. Use the transcript prompt-cost proxy fields to prioritize repeated long
+   prompts that are likely worth turning into a shared resource.
+7. Treat those prompt-cost fields as triage signals, not as exact billing data.
+6. Before asking for a decision, explain the candidate's likely purpose,
+   concrete benefit, audit context, and score rationale. If evidence is thin,
+   call that out explicitly instead of asking the user to infer it.
+8. Promote only candidates that map cleanly to a portable skill, instruction,
+   prompt adapter, agent, hook, script, or template.
+9. After rows are approved, run `resources/scripts/prepare-audit-promotions.sh`
+   to create draft resources or staging notes in the audit directory.
+10. Keep non-portable or repo-specific findings in audit notes rather than
+   forcing them into shared resources.
+
+## Outputs
+
+- `audit-summary.md` — high-level run summary and top candidates
+- `candidates-report.tsv` — scored candidate list with source references
+- `selection-manifest.tsv` — editable approval surface for promotion decisions
+- `pattern-details/*.md` — per-candidate evidence bundles with benefit, context, score rationale, and caveats
+- `draft-resources/` — generated draft resource files for approved portable rows
+- `staging-notes/` — generated follow-up notes for approved rows that still need design work
+
+## Notes
+
+- The runner is macOS-first in this iteration.
+- Audit history is stored per machine under `.local/audits/<machine-id>/` in the
+  repo checkout and is intentionally git-ignored.

resources/skills/resource-authoring/references/publishing-checklist.md

@@ -5,3 +5,9 @@
 - Confirm frontmatter is valid and descriptive.
 - Avoid duplicating a workflow that already exists.
 - If scripts are referenced, validate them before merging.
+- Check whether the same outcome can be achieved with a cheaper shared
+	primitive or by reusing an existing resource.
+- Keep examples and embedded guidance short unless the extra context is
+	essential.
+- Say when the resource should not be used if that prevents wasteful generic
+	usage.