agentleFS
MrPunyapalMrPunyapal/laravel-auditor/.agents/skills/package-generate-skill/SKILL.md

package-generate-skill

Skill78 starsChanged 3 months agoMITView on GitHub

Use this skill when creating or updating the bundled Laravel Boost skill under resources/boost/skills from the package implementation and package documentation. Trigger after public APIs, commands, config, routes, views, publish tags, README content, or examples change.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 8 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep the package's bundled Boost skill accurate, concise, and focused on helping Laravel applications adopt the package.

    line 13
  2. Very specific:

    Update resources/boost/skills/*/SKILL.md with practical adoption steps, references, examples, and anti-patterns for Laravel app developers …

    line 20
  3. Distinctive:

    Write for consumers installing the package in a Laravel application, not for maintainers changing package internals.

    line 26
  4. Distinctive:

    Prefer short, task-oriented steps over broad explanations.

    line 27
  5. Distinctive:

    Keep examples runnable and aligned with documented package names, config keys, commands, and publish tags.

    line 29
  6. Distinctive:

    Keep the skill small enough for an agent to load and apply quickly.

    line 30
  7. Distinctive:

    After adding a new Artisan command, update the Boost skill with when to run it, required options, expected output, and any related config.

    line 46
  8. Distinctive:

    After adding config and publish tags, update the Boost skill with publish commands and the minimum config keys users need to set.

    line 47
  9. Distinctive:

    After adding a facade or public class, update the Boost skill with one practical integration example and the test assertion a consuming app …

    line 48

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Package Generate Skill

Primary Goal

Keep the package's bundled Boost skill accurate, concise, and focused on helping Laravel applications adopt the package.

Workflow

  1. Inspect the package implementation before editing the Boost skill: service provider, facades, public classes, commands, config, routes, migrations, events, views, publish tags, and tests.
  2. Inspect package documentation: README.md, contributing docs, examples, and changelog entries that describe user-facing behavior.
  3. Identify the public integration surface only. Include install, configure, publish, command, route, facade, helper, middleware, event, and testing guidance only when the package actually exposes it.
  4. Update resources/boost/skills/*/SKILL.md with practical adoption steps, references, examples, and anti-patterns for Laravel app developers using the package.
  5. Preserve front matter, package metadata, and the Boost skill structure: description, primary goal, workflow, references, examples, and anti-patterns.
  6. Validate that the Boost skill does not describe internals as public API and does not document features that are not implemented.

Writing Rules

  • Write for consumers installing the package in a Laravel application, not for maintainers changing package internals.
  • Prefer short, task-oriented steps over broad explanations.
  • Point to concrete files only when they help the consumer understand package adoption.
  • Keep examples runnable and aligned with documented package names, config keys, commands, and publish tags.
  • Keep the skill small enough for an agent to load and apply quickly.

References

  • resources/boost/skills/
  • src/*ServiceProvider.php
  • src/Facades/
  • src/Console/Commands/
  • config/*.php
  • routes/*.php
  • database/migrations/
  • README.md
  • tests/Feature/ and tests/Unit/

Examples

  • After adding a new Artisan command, update the Boost skill with when to run it, required options, expected output, and any related config.
  • After adding config and publish tags, update the Boost skill with publish commands and the minimum config keys users need to set.
  • After adding a facade or public class, update the Boost skill with one practical integration example and the test assertion a consuming app should use.

Anti-Patterns

  • Regenerating the Boost skill from documentation alone without checking implementation.
  • Documenting private classes, test helpers, workbench-only routes, or implementation details as consumer API.
  • Adding speculative examples for features the package does not provide.
  • Removing package metadata that consuming agents need to identify and apply the skill.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.