laravel-filament
Filament v5 admin-panel reference skill: resources, forms, tables, actions, filters, relation managers, widgets, panels, and testing. Use when the task touches Filament-specific admin code and needs the v5 namespace and API conventions rather than generic Laravel patterns.
What this skill does
<EXTREMELY-IMPORTANT> This skill exists to keep Filament work aligned with v5, not to duplicate the entire reference library. Non-negotiable rules: 1. Read `references/namespaces.md` first. 2. Then load only the reference files the task actually needs. 3. Keep business logic out of Resources. 4. Use the v5 action and table APIs, not old v3 patterns. 5. Keep the heavy Filament cookbook in `references/`, not inline here. </EXTREMELY-IMPORTANT> # laravel-filament ## Inputs - `$request`: The Filament admin task or component to modify ## Goal Route Filament work through the correct v5 conventions so the implementation uses the right namespaces, table APIs, and admin-panel composition patterns. ## Step 0: Read the v5 namespace contract Always start with: - `references/namespaces.md` That establishes the namespace and API changes that commonly break Filament work. **Success criteria**: The task is grounded in the correct Filament v5 surface before editing. ## Step 1: Load only the relevant admin references Use the routing table to pick reference files. Do not bulk-load everything. | Task | Read | |------|------| | v5 namespace and API changes | `references/namespaces.md` | | Creating or editing a Resource (CRUD) | `references/resources.md` | | Form fields, sections, layout | `references/forms.md` | | Table columns, sorting, searching | `references/tables.md` | | Bulk actions, row actions, header actions | `references/actions.md` | | Table filters, filter forms | `references/filters.md` | | Relation managers, BelongsToMany, HasMany | `references/relationships.md` | | Dashboard widgets, stats, charts | `references/widgets.md` | | Multi-panel setup, navigation, tenancy | `references/panels.md` | | Flash messages, database notifications | `references/notifications.md` | | Infolist entries, read-only views | `references/infolists.md` | | Testing resources, pages, actions | `references/testing.md` | Multiple tasks? Read multiple files. **Success criteria**: Only the task-relevant Filament conventions are in the active context. ## Step 2: Implement with the core Filament guardrails Keep these rules active: - actions come from `Filament\\Actions\\*` - tables use the v5 record/toolbar/header action methods - badge presentation uses `TextColumn->badge()` - layout components come from the Schemas package - Resource classes delegate real business work to application Actions **Success criteria**: The change uses valid v5 APIs and stays maintainable. ## Step 3: Verify the admin surface Use the narrowest relevant verification: - focused feature tests - Filament page/resource tests - lightweight UI smoke coverage if the repo already has it **Success criteria**: The Filament surface still behaves correctly after the change. ## Guardrails - Do not inline the whole Filament handbook in `SKILL.md`. - Do not skip `references/namespaces.md`. - Do not use v3 action namespaces or deprecated table methods. - Do not put business logic directly in Resource classes. ## When To Load References - `references/namespaces.md` Always. - then only the task-relevant files under `references/` ## Output Contract Report: 1. which Filament references were loaded 2. the v5 pattern applied 3. the change made 4. the verification run
Related in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.