- How do I install llm/skills in a Laravel project?
- Run `composer require --dev llm/skills` in your Laravel project. Composer will prompt to enable the plugin—confirm with **y**. For non-interactive setups, add `"allow-plugins": { "llm/skills": true }` to your `composer.json` under the `config` key.
- What Laravel versions does llm/skills support?
- The package is PHP-centric and works with any Laravel version (5.8+) since it integrates via Composer. Ensure your PHP version matches the skill dependencies. Test thoroughly if using Laravel-specific integrations like Artisan commands.
- Can I use llm/skills for runtime AI agents in Laravel?
- Yes, but skills are primarily designed for developer tooling (e.g., IDE hints, CLI commands). For runtime use, integrate with Laravel’s service container or Artisan commands to trigger skills dynamically. Example: Register a `SkillServiceProvider` to resolve skills as Laravel services.
- How do I add a skill from a Git repository (not Composer)?
- Use the `skills:add` command followed by the repository URL (e.g., `composer skills:add https://github.com/user/skill-repo`). The skill will sync to `.agents/skills/` automatically. Verify with `composer skills:list`.
- Are there security risks with arbitrary Git skills?
- Yes. Malicious skills could inject prompts or execute code. Mitigate by enforcing `"trusted-replace": true` in production, auditing skills with `composer skills:show --verbose`, and using signed Composer packages. Avoid untrusted repositories in CI/CD.
- How do I disable auto-sync during `composer install`?
- Add `"auto-sync": false` to your `skills.json` config. This prevents skills from syncing automatically, reducing CI/CD build times. Manually sync with `composer skills:update` when needed.
- Can I integrate skills with Laravel’s service container?
- Yes. Create a `SkillServiceProvider` to bind skills as Laravel services. Example: Register a `SkillResolver` that loads `SKILL.md` files dynamically. This enables skills to interact with Laravel’s dependency injection system.
- How do I test skills in a Laravel project?
- Unit test `SKILL.md` content with PHP parsers (e.g., `symfony/yaml` for YAML skills). For Laravel-specific integrations, write integration tests using Laravel’s HTTP layer or Artisan commands. Cache skills in CI with `composer skills:update --no-dev`.
- What if two skills have the same directory name?
- Skills are identified by their directory names, so conflicts will overwrite files. Resolve this by using unique namespaces (e.g., `vendor/skill-name`) or merging skills manually. Audit with `composer skills:show --verbose` to detect duplicates.
- Are there alternatives to llm/skills for Laravel AI workflows?
- For Laravel-specific AI integrations, consider packages like `laravel-ai` or custom solutions using Laravel’s HTTP layer to expose skills as APIs. For Composer-based skill distribution, alternatives are limited—llm/skills is the only plugin offering Git/Composer hybrid support.