jrgilbertson/the-rookery

creating-portable-skills

Create, revise, migrate, or audit portable Agent Skills packages.

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/jrgilbertson/the-rookery --skill creating-portable-skills

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

Creating Portable Skills

Produce an installable package that does the user's reusable job and follows the Agent Skills specification. Add behavioral evals when observed failures warrant them under the host's evaluation policy.

For a read-only audit, apply references/review-checklist.md and return prioritized findings with file evidence and a verdict. For authorized creation, revision, or migration, use the workflow below. Existing authorization and the host project's constraints carry forward.

Author the package

Ground the skill in the user's intent, existing package, representative inputs and outputs, and corrections from real work. Identify the outcome and hard constraints that make completion acceptable. Check the host's contribution rules, discovery path, and existing owners before adding a workflow or helper.

For a new skill, use assets/skill-template.md. For a revision, the last commit can preserve the prior version. For a migration, revise a copy and preserve the source. Read references/portability.md when choosing frontmatter, bundling dependencies, or removing harness-specific assumptions.

Keep one instruction set for the job. Separate changing facts from reusable instructions when that lets the next update change one source. Put conditional guidance in references/, copied outputs in assets/, and deterministic helpers in scripts/ when an existing mechanism cannot meet the requirement. Bundle everything the package needs, or declare its actual environment dependencies.

Apply references/review-checklist.md while drafting. Preserve user authority, exact formats, privacy requirements, and fragile operation order; leave reasoning and implementation choices open.

Validate and evaluate

Use skills-ref validate <skill-directory> from an available trusted install. If it is unavailable, check the specification's frontmatter rules, name-directory match, body, and local resource links directly, and record the limitation. Exercise bundled helpers with realistic inputs in disposable storage outside the host project; preserve existing inputs and outputs.

Package checks, helper tests, and applicable authorized smoke checks run for every package. For behavioral evaluation, follow references/evaluation.md.

Deliver

Check the final package's local links, dependencies, host conventions, and applicable evaluation evidence. Report the package location, observed checks, and anything unverified. For public migrations, replace private examples with synthetic inputs that preserve the behavior and difficulty being tested, and inspect the whole copy for leaks. Keep answers and grading material outside the runtime instructions. Follow the host's release and installation process.

Sources

The Agent Skills specification owns the package format. references/evaluation.md owns evaluation and names the upstream workflows it uses.

from this repository

More skills

All skills
jrgilbertson
Community

checking-simplicity

Use when the user asks to simplify, right-size, identify overengineering, compare with a stated smaller alternative, choose the smallest viable approach, check for simplicity as well, or test whether reuse removes the need for change on a named architecture, design, area, plan, technical choice, or code-level approach. General architecture comparison or product brainstorming without that simplification intent stays with planning. Also use during a build or plan-to-build handoff when the next ste

1h installs
2
GitHub stars
14
Updated
Nov 3
jrgilbertson
Community

coordinating-work

Establish or revive an Orca collaboration arrangement, including Planner, Coordinator, and task workers. Use when explicitly asked to set up a team or recover existing collaboration after an account or session interruption. Ordinary CE execution and small child-worktree delegation keep their existing workflows.

1h installs
2
GitHub stars
14
Updated
Nov 3
jrgilbertson
Community

managing-issues

Use when the requested outcome is reading, drafting, creating, or surgically updating GitHub or Linear issue records; changing their native parent, sub-issue, or blocker relationships and assessing readiness; checking completion against Verification evidence; or reversibly closing or canceling an issue. Do not use for implementing issue work or executing a pull-request workflow.

1h installs
2
GitHub stars
14
Updated
Nov 3
jrgilbertson
Community

managing-personal-crm

Use when the user asks to capture a relationship interaction, prepare for one person, clean up or reconstruct Person notes, review overdue relationships, discover who could help with current work, when another workflow finds a possible relationship effect, or when the user later confirms or revises a required catch-up source inventory, supplies stage-one dispositions, continues visible stage-two reconstruction by confirming or correcting an interpretation, answering a focused question, or resumi

1h installs
2
GitHub stars
14
Updated
Nov 3