spatie-package-skeleton
Guide for creating PHP and Laravel packages using Spatie's package-skeleton-laravel and package-skeleton-php templates. Use when the user wants to create a new PHP or Laravel package, scaffold a package. Also use when building customizable packages — covers proven patterns for extensibility (events, configurable models/jobs, action classes) instead of config option creep.
85
Quality
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong description that clearly identifies its niche (PHP/Laravel package development with Spatie templates) and includes explicit 'Use when' triggers. The main weakness is that the specific actions/capabilities could be more concrete - it describes what the skill covers conceptually but doesn't enumerate specific operations the skill enables.
Suggestions
Add more concrete actions like 'generate package boilerplate', 'configure composer.json', 'set up PHPUnit testing', or 'publish package to Packagist' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (PHP/Laravel packages) and mentions specific templates (Spatie's package-skeleton-laravel and package-skeleton-php), but the actions are somewhat vague - 'creating', 'scaffold', 'building customizable packages' without listing concrete operations like 'generate boilerplate', 'configure autoloading', or 'set up testing'. | 2 / 3 |
Completeness | Clearly answers both what (guide for creating PHP/Laravel packages using Spatie templates, covers extensibility patterns) AND when (explicit 'Use when' clause specifying 'create a new PHP or Laravel package, scaffold a package' and 'building customizable packages'). | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'PHP', 'Laravel', 'package', 'scaffold', 'create', 'Spatie', 'extensibility', 'events', 'configurable models', 'action classes'. These are terms developers would naturally use when seeking help with package development. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche - PHP/Laravel package creation using Spatie templates. The combination of 'package-skeleton-laravel', 'package-skeleton-php', and extensibility patterns (events, configurable models/jobs, action classes) creates a distinct trigger profile unlikely to conflict with general PHP or Laravel skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable skill with excellent workflow clarity and executable examples. The main weakness is that it combines two distinct concerns—package scaffolding workflow and package design patterns—into one document, making it longer than necessary. Some explanatory content about obvious practices could be trimmed.
Suggestions
Split 'API Design Principles' and 'Package Patterns' sections into a separate PATTERNS.md reference file, keeping SKILL.md focused on the scaffolding workflow
Remove obvious guidance like 'Use well-named methods' and 'Method names should be intuitive' that Claude already knows
Condense the 'Gather Package Details' section—the defaults explanation could be a simple list rather than prose
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundant explanations (e.g., explaining what vendor name means, listing obvious defaults). The API Design Principles and Package Patterns sections are valuable but could be more condensed—some patterns like 'use well-named methods' state obvious best practices Claude already knows. | 2 / 3 |
Actionability | Provides fully executable bash commands, complete PHP code examples, and specific file paths. The sed replacement commands, file renaming steps, and service provider configuration are all copy-paste ready with concrete examples. | 3 / 3 |
Workflow Clarity | Clear 6-step workflow with explicit sequencing, includes a critical WARNING about stdin piping issues, provides verification steps after setup, and specifies timeout considerations for composer install. The workflow has appropriate checkpoints and error prevention. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the skill is monolithic—the extensive 'Package Patterns' section (covering events, configurable models, testing fakes, etc.) could be split into a separate reference file. The skill tries to cover both scaffolding workflow AND design patterns in one document. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 9 / 11 Passed | |
- Repository
- freekmurze/dotfiles
- Commit
355d067
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.