dboeckli/ai-agent-skills

camel-matrix

Generates a Markdown compatibility matrix for Apache Camel Spring Boot, Spring Boot, and Apache CXF versions by running the camel-springboot-matrix.sh script.

Ver código fuente

Cómo usar

  1. Copia el comando y revisa el paquete antes de instalarlo en tu entorno de agente.
  2. Consulta las herramientas, credenciales y entornos necesarios en el documento original.
  3. Describe las entradas y el resultado deseado; contrasta la salida con las fuentes.
npx skills add https://github.com/dboeckli/ai-agent-skills --skill camel-matrix

Antes de empezar

  • La instalación no incluye suscripción al modelo, cuota API ni permisos sobre tus archivos.
  • Las estrellas e instalaciones reflejan actividad, no una prueba independiente de calidad o seguridad.
Documento original del Skill

Contenido del repositorio de origen con títulos, ejemplos, código, tablas, enlaces e imágenes preservados.

Camel Spring Boot Compatibility Matrix

Run scripts/camel-springboot-matrix.sh (bundled in this skill) to generate target/camel-springboot-matrix.md relative to the current project directory. The target/ directory is created automatically if it does not exist.

Arguments

The user may provide an optional version range: $ARGUMENTS

  • No arguments: use the default range 4.14.0 to latest (see below)
  • Two arguments (e.g. 4.0.0 4.15.0): only versions in that range are processed

Steps

  1. Run the script. If no version range is given by the user, default to 4.14.0 as minimum and omit the max argument (so the script fetches up to the latest available version):
bash
bash "${CLAUDE_PLUGIN_ROOT}/scripts/camel-springboot-matrix.sh" ${ARGUMENTS:-4.14.0}
  1. After completion, report:
  • How many Camel versions were processed
  • That target/camel-springboot-matrix.md was created/updated in the current project directory
  • The last 5 rows of the generated table so the user can verify the output

Relacionados por tarea

del mismo repositorio

Más Skills

Todos los Skills
dboeckli
Comunidad

cc-best-practices

Guidance on how to use Claude Code effectively — covering context management, verification strategies, the explore-plan-implement workflow, prompting techniques, session management, parallel sessions, and common failure patterns. Use this skill whenever the user asks how to get the most out of Claude Code, how to write better prompts, how to manage context, when to use plan mode, how to automate tasks, or when they describe a frustrating pattern like Claude repeating mistakes or losing track of

Instalaciones / 1h
18
GitHub Stars
0
Actualizado
29 sept
dboeckli
Comunidad

cron-schedule-planner

Builds an overview of GitHub Actions schedule cron expressions across multiple repositories and helps spread CPU-intensive jobs (Docker Compose, Testcontainers, Kind/k3s, matrix builds) into less contended slots. Use when the user asks 'when do my cron actions run?', 'do my scheduled builds collide?', 'when should the Testcontainers build run?', or wants a cron schedule overview/distribution report across repos. Scans via gh (no local checkouts required) or local checkouts, converts UTC to a loc

Instalaciones / 1h
18
GitHub Stars
0
Actualizado
29 sept
dboeckli
Comunidad

skill-best-practices

Guide for creating, structuring, and improving Claude skills (SKILL.md). Use when building a new skill, reviewing an existing skill, writing SKILL.md frontmatter, defining trigger conditions, troubleshooting skill problems (not triggering, over-triggering, instructions not followed), or planning skill distribution. When working on any skill in this repository: also load the cc-best-practices skill, and always update both CLAUDE.md and README.md skill tables after any skill change. Do NOT use for

Instalaciones / 1h
18
GitHub Stars
0
Actualizado
29 sept
dboeckli
Comunidad

project-references

Look up conventions, patterns, and concrete implementations from your own GitHub repositories checked out locally under ~/projects/referenzen/. Use this skill whenever there is uncertainty about how something is done in your codebase family — e.g. Helm chart structure, Kubernetes manifests, framework configuration patterns, Docker Compose conventions, CI/CD pipeline setup, or any other recurring architectural decision. Invoke it proactively before guessing at a convention; always cite the source

Instalaciones / 1h
18
GitHub Stars
0
Actualizado
29 sept