provider-compatibility
Skill0 starsChanged 2 months agoMITView on GitHub
Research and implement subscription-aware ACP or native agent adapters and explicit OpenAI or Anthropic-compatible API endpoints without conflating authentication, entitlement and transport.
In this repository39 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- adaptSkill
- agentos-builderSkill
- agentos-verifySkill
- agent-runtimeSkill
- animateSkill
- application-integrationSkill
- arms-architectureSkill
- arrangeSkill
- auditSkill
- bolderSkill
- capability-policySkill
- capture-to-planSkill
- clarifySkill
- colorizeSkill
- composer-and-voiceSkill
- composer-designSkill
- critiqueSkill
- delightSkill
- distillSkill
- evidence-reviewSkill
- extractSkill
- frontend-designSkill
- hardenSkill
- memory-routingSkill
- normalizeSkill
- onboardSkill
- optimizeSkill
- overdriveSkill
- polishSkill
- quieterSkill
- routine-engineeringSkill
- skill-authoringSkill
- spatial-designSkill
- teach-impeccableSkill
- typesetSkill
- widget-contractSkill
- custom-workflowSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 6
Read the compatibility guide and source patterns.
- Distinctive: line 9
Verify current official documentation, installed version, supported transport and account entitlement independently.
- Distinctive: line 11
Use an isolated project runtime.
- Distinctive: line 12
Add one opt-in adapter with explicit limits and no automatic login, billing fallback or credential copying.
- Distinctive: line 13
Test protocol normalization with fixtures, then an authorized live prompt, cancellation/denial and restart.
- Distinctive: line 14
Update the dated compatibility matrix and provider contract.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Read the compatibility guide and source patterns.
- Identify the exact provider instance, desired agent/model lane and source of authority for credentials.
- Verify current official documentation, installed version, supported transport and account entitlement independently.
- Record native versus bridged ACP, authentication owner, billing route, model capabilities and policy restrictions.
- Use an isolated project runtime; never assume ACP capability flags sandbox native tools or block inherited hooks.
- Add one opt-in adapter with explicit limits and no automatic login, billing fallback or credential copying.
- Test protocol normalization with fixtures, then an authorized live prompt, cancellation/denial and restart. Keep evidence levels explicit.
- Update the dated compatibility matrix and provider contract; preserve original source references and unresolved differences.
For representative and failure cases, read the evaluation guide. Use the quickstart for the implemented runtime path and run python3 scripts/smoke_template.py to verify a fresh copy.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.