Use when working with Laravel Pennant the official Laravel feature flag package. Trigger whenever the query mentions Pennant by name or involves feature flags or feature toggles in a Laravel project. Tasks include defining feature flags checking whether features are active creating class based features in `app/Features` using Blade `@feature` directives scoping flags to users or teams building custom Pennant storage drivers protecting routes with feature flags testing feature flags with Pest or PHPUnit and implementing A B testing or gradual rollouts with feature flags. Do not trigger for generic Laravel configuration authorization policies authentication or non Pennant feature management systems.
83
76%
Does it follow best practices?
Impact
97%
1.06xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.ai/pennant/skill/pennant-development/SKILL.mdFeature flag definition and scoped user checks
Correct namespace import
100%
100%
Feature::define() usage
83%
91%
Closure receives scope
100%
100%
Boolean return from closure
100%
100%
Global feature check
50%
100%
Scoped feature check
66%
100%
Kebab-case naming
100%
100%
No scope forgotten in check
100%
100%
Feature defined before use
100%
100%
Blade @feature directive with @else/@endfeature
@feature directive used
100%
100%
@else branch present
100%
100%
@endfeature closes block
100%
100%
New component inside feature
100%
100%
Legacy component in else branch
100%
100%
Correct feature name used
100%
100%
No prohibited approach
100%
100%
Both variants wrapped
100%
100%
Explanation in notes.md
100%
100%
Feature activation global and scoped with verification tests
Global activate call
83%
50%
Scoped activate call
100%
100%
Feature::define() present
30%
100%
Correct namespace import
100%
100%
Test inactive by default
100%
100%
Test active after user activation
100%
100%
Test active after global activation
100%
100%
Multiple scope coverage
100%
100%
Kebab-case feature name
40%
100%
9c28875
Table of Contents
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.