The Agent Skills Directory

[DYNAMIC_CONTEXT_INJECTION]: The skill uses the ! dynamic context injection syntax in scripts/create-ci-pipeline.md and scripts/create-docker-compose.md. These shell commands (e.g., grep, ls, test) are used to auto-detect the project's technical stack, such as the programming language, versions, and existing workflows. This information is then used to populate the generated CI/CD and Docker configuration templates, facilitating automation.
[CREDENTIALS_UNSAFE]: Hardcoded default credentials (e.g., POSTGRES_USER: postgres and POSTGRES_PASSWORD: postgres) are present in scripts/docker-compose.yml and the scripts/create-docker-compose.md template. These are documented as local development defaults for prototyping and are not a threat if replaced by secrets management in production as recommended in the skill's own documentation.
[INDIRECT_PROMPT_INJECTION]: The skill has a surface for indirect prompt injection as it reads project-specific files like package.json and pyproject.toml using shell commands and injects their output into the prompt for template creation.
Ingestion points: File content extracted via grep commands in scripts/create-ci-pipeline.md and scripts/create-docker-compose.md.
Boundary markers: The skill uses markdown and YAML structures to separate auto-detected data from instructions, which provides a basic level of context isolation.
Capability inventory: The skill possesses the ability to write new configuration files to the repository and provides guidance for executing deployment commands.
Sanitization: The shell commands utilize specific regex patterns to extract only relevant version numbers or keywords, limiting the amount of raw untrusted data injected into the context.
[COMMAND_EXECUTION]: The skill scripts and documentation reference the use of high-privilege CLI tools such as docker, kubectl, helm, terraform, and the railway CLI. These are required for the skill's primary function of infrastructure management and application deployment.
[EXTERNAL_DOWNLOADS]: Example GitHub Actions workflows in scripts/github-actions-pipeline.yml reference several third-party actions from trusted organizations such as GitHub and Aqua Security. These are standard, well-known components for CI/CD pipelines.

devops-deployment