Skip to content
cccskills
FreePublished on GitHub

new-provider

Adds an AI provider to hermesllm by updating provider identifiers, parsing, request and response types when needed, model lists, and API mappings. It then runs the library tests to check that the changes compile and pass.

OriginalShow the original description

Add a new LLM provider to hermesllm. Use when integrating a new AI provider.

katanemo/plano7,101 stars(GitHub 7,101 + cccskills 0)

Run score Not tested

See how to install

Good for

  • Integrating a new AI provider into hermesllm
  • Adding provider-specific API request and response types
  • Updating supported models and upstream API mappings
  • Checking provider changes with library tests

Files included (1)

  • SKILL.md866 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

Add a new LLM provider to hermesllm. The user will provide the provider name as $ARGUMENTS.

  1. Add a new variant to ProviderId enum in crates/hermesllm/src/providers/id.rs
  2. Implement string parsing in the TryFrom<&str> impl for the new provider
  3. If the provider uses a non-OpenAI API format, create request/response types in crates/hermesllm/src/apis/
  4. Add variant to ProviderRequestType and ProviderResponseType enums and update all match arms
  5. Add model list to crates/hermesllm/src/providers/provider_models.yaml
  6. Update SupportedUpstreamAPIs mapping if needed

After making changes, run cd crates && cargo test --lib to verify everything compiles and tests pass.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Builds the brightstaff native binary in release mode after code changes. If compilation fails, it diagnoses the build errors and fixes them so the binary can be produced.

  • Building brightstaff after changing its code
  • Diagnosing a failed brightstaff release build
  • Fixing compilation errors in brightstaff
katanemo/plano7.1KUpdated Oct 25, 2026

build-cli

FreeSummary

Build and install the `planoai` Python CLI locally after changes to its `cli/` code. It syncs the project dependencies, installs the package in editable mode, and checks that the command starts and displays its help.

  • Installing the CLI after editing its source
  • Checking that `planoai` starts and shows help
  • Diagnosing a local build or installation failure
katanemo/plano7.1KUpdated Oct 25, 2026

build-wasm

FreeSummary

Builds the Envoy WASM plugins for llm_gateway and prompt_gateway after code changes. If the build fails, it diagnoses and fixes the errors so the plugins can be compiled for the wasm32-wasip1 target.

  • Building Envoy WASM plugins after code changes
  • Compiling llm_gateway and prompt_gateway
  • Diagnosing failed WASM plugin builds
katanemo/plano7.1KUpdated Oct 25, 2026

check

FreeSummary

Check Rust changes by running formatting validation, Clippy linting, and library unit tests in order. It can fix formatting issues, asks for warnings to be resolved, and reports which checks passed or failed.

  • Checking Rust changes before review
  • Running formatting, lint, and unit checks
  • Finding code warnings after an edit
katanemo/plano7.1KUpdated Oct 25, 2026

Design advanced Plano architectures for distinct listeners and layered orchestration. Tighten prompt target schemas, reduce ambiguity in tool calls, and shape migration-safe recommendations with scenarios to check the design.

  • Planning a Plano system with multiple distinct listeners
  • Clarifying prompt target parameters and schemas
  • Combining model, prompt, and agent listeners
katanemo/plano7.1KUpdated Oct 25, 2026

Improve Plano multi-agent orchestration by checking agent registration and listener wiring, refining capability-focused descriptions, and defining fallback behavior. Get example prompts for validating that requests reach the intended agent.

  • Troubleshooting inaccurate routing across multiple agents
  • Checking agent and listener configuration consistency
  • Writing concise, capability-focused agent descriptions
katanemo/plano7.1KUpdated Oct 25, 2026

See all skills by katanemo

Report a problem with this skill