Download the PHP package sandermuller/boost-skills without Composer
On this page you can find all versions of the php package sandermuller/boost-skills. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download sandermuller/boost-skills
More information about sandermuller/boost-skills
Files in sandermuller/boost-skills
Package boost-skills
Short Description A package that ships AI skills to be used for shipping code in both packages and projects
License MIT
Homepage https://github.com/sandermuller/boost-skills
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package boost-skills
boost-skills
Sander Muller's personal Composer-distributed catalog of AI agent skills for PHP projects and Composer packages. Adopt it if your preferences align with Sander's, or use it as a template for your own.
No runtime code — pure Markdown. A sync engine (sandermuller/boost-core or laravel/boost) reads the skills and always-on guidelines in the catalog and writes them into every AI agent directory you have configured: Claude Code, Cursor, Copilot, Codex, Gemini, and the rest.
Documentation: https://sandermuller.github.io/boost-core/packages/boost-skills/
Install
Install the catalog beside the family package for your role — the picker settles which in two questions:
Then allowlist the vendor — a catalog ships nothing until you name it:
vendor/bin/boost tags lists what a further tag would unlock.
Under laravel/boost instead, follow its setup and include this package in what it syncs. Tag filtering and Project Conventions slots are inert there; skills carry visible defaults, so a slot still reads sensibly.
In every project
To use some skills outside a project, install the catalog globally and list the skills you want in ~/.boost/user-scope.php (needs boost-core >= 1.13.0):
Each skill is published with a -user suffix, for example /interview-user, so it never hides a project's own copy. A listed skill also brings the skills it names in boost-requires. A package with no entry publishes every skill. User scope has no boost.php, so tags do not apply and conventions slots show their defaults. See Choose user-scope skills.
Documentation
| Topic | Page |
|---|---|
| Adopting the catalog, editing a skill | Overview |
| The same inventory, rendered | Skill catalog |
| Where skills come from, and which gates apply | Skill sources |
How tags and boost-requires work |
Tags and dependencies |
| The conventions slot mechanism | Project Conventions |
| Shipping scripts beside a skill | Skill assets |
Re-syncing on composer install |
Automating the sync |
Catalog
The package ships skills, always-on guidelines and Claude Code subagents. Most content is universal. The rest carries capability tags: a project declares what it has in boost.php via ->withTags(...), and only matching content syncs.
CATALOG.md lists every skill, tag, guideline and subagent, with its tags.
Already wrote a subagent yourself? Claude Code picks a subagent by its frontmatter name, so a local .claude/agents/tech-lead-reviewer.md and the shipped one clash. Delete or rename yours; boost sync warns until you do.
Editing skills and guidelines
Skills are resources/boost/skills/<name>/SKILL.md with name + description frontmatter. Guidelines are resources/boost/guidelines/<name>.md with no frontmatter — they must open at a heading to render under both engines.
Edit them here, never in a consuming project's synced copy — boost-core overwrites that on the next sync. The ai-guidelines skill carries the frontmatter contract.
Changelog
See CHANGELOG.md for release history.
Security
Found a vulnerability? Email [email protected] rather than opening a public issue. See SECURITY.md for the disclosure policy.
Skill scanners report findings here
Static skill scanners such as SkillSpector flag this package. The findings are false positives. Three patterns cause them:
- HTML comments read as prompt injection. A
<!--boost:conv …-->token is aboost-coreplaceholder that the sync resolves, and<!-- verified-sha: … -->and<!-- spec:planned-at … -->are anchors. A scanner cannot tell them from a hidden instruction. - Anti-pattern prose read as an instruction. A skill that lists "without asking" or "skip verification" as a thing not to do matches the same string as a skill that tells an agent to do it.
- Documented shell commands read as tool misuse. The
autoresearchskill printsgit reset --hard HEAD~1because its loop commits before it measures, so a rejected experiment reverts in one step.
Do not add a scanner baseline file to this repository. A baseline written by the package author suppresses the findings in a consumer's own scan, which is why SkillSpector ignores a discovered baseline until the consumer opts in.
Credits
License
MIT. See LICENSE.
