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.
71
88%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%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 skill description that clearly identifies its niche (PHP/Laravel package creation with Spatie templates), lists concrete capabilities including extensibility patterns, and provides explicit 'Use when' triggers. It uses proper third-person voice and covers both the scaffolding use case and the design patterns use case, making it easy for Claude to select appropriately.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions and patterns: creating packages using specific templates (Spatie's skeleton), scaffolding, and covers extensibility patterns like events, configurable models/jobs, and action classes. These are specific, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (guide for creating PHP/Laravel packages using Spatie templates, covers extensibility patterns) and 'when' (explicit 'Use when' clause covering creating new packages, scaffolding, and building customizable packages). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'PHP', 'Laravel', 'package', 'scaffold', 'Spatie', 'package-skeleton-laravel', 'package-skeleton-php', 'extensibility', 'events', 'configurable models'. Good coverage of terms a developer would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a specific niche (PHP/Laravel package creation using Spatie's templates) with clear triggers. Unlikely to conflict with general PHP development or Laravel application skills due to the specific focus on package authoring and Spatie's tooling. | 3 / 3 |
Total | 12 / 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 a well-sequenced workflow and excellent concrete guidance for scaffolding Laravel packages. Its main weakness is length — the extensive 'Package patterns' section, while valuable, inflates the token cost and would be better served as a separate reference file. Some design advice (early returns, no else statements, well-named methods) is general knowledge that doesn't need restating.
Suggestions
Extract the 'Package patterns' and 'API Design Principles' sections into a separate PATTERNS.md file and reference it from the main skill to reduce token cost.
Remove guidance Claude already knows (e.g., 'use well-named methods', 'do not use else statements', 'return early instead') or consolidate into a brief reference to the spatie php-guidelines skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly long (~300 lines) and includes some content Claude would already know (e.g., API design principles like 'use well-named methods', 'sensible defaults', early returns). The workflow section is efficient, but the extensive 'Package patterns' section reads more like a general design guide than task-specific instruction. Some patterns (Conditionable, Macroable) are briefly mentioned without needing explanation. | 2 / 3 |
Actionability | The workflow section provides fully executable bash commands and PHP code snippets that are copy-paste ready. The sed replacement commands, file rename operations, and verification steps are concrete and specific. The package patterns section also includes executable PHP examples rather than pseudocode. | 3 / 3 |
Workflow Clarity | The 6-step workflow is clearly sequenced with explicit steps: gather details → create repo → configure (with a critical WARNING about stdin piping) → verify setup → commit/push → report. The verification step acts as a checkpoint, and the warning about configure.php is an important validation/error-prevention measure for a destructive operation. | 3 / 3 |
Progressive Disclosure | The content is a monolithic file with no references to supporting files, despite being long enough to benefit from splitting. The 'Package patterns' section (~150 lines of design guidance) could easily be a separate reference file. The workflow and post-setup reference are well-structured with headers, but everything is inline 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
3974caa
- 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.