Agent skill
security-patterns
Use this skill when working on credentials, secrets, environment variables, Docker security, or any security-related concern. Triggers on: secrets management, credential handling, Docker security, environment variables, or mentions of "security", "secrets", "credentials", "env vars", or "vulnerability".
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/security-patterns-codehalwell-doclingoptimisation
SKILL.md
Security Patterns — DoclingOptimisation
Secrets Management
- Environment variables for all runtime configuration (DOCLING_* vars)
- Never hardcode API keys, tokens, or credentials in code
- Docker Hub credentials via GitHub Secrets in CI/CD
- Azure Container App secrets for runtime environment variables
Docker Security
- Non-root user (
docling:docling) in runtime image - No dev dependencies in runtime stage
- Minimal runtime packages (only what's needed)
- No shell access in production (consider
--no-install-recommends) - Pin base image versions to prevent supply chain attacks
Model Downloads
- Models pre-fetched at build time from HuggingFace Hub and ModelScope CDN
HF_HUB_ETAG_TIMEOUT=0andHF_HUB_DOWNLOAD_TIMEOUT=5prevent runtime downloads- Verify model integrity if moving to a private registry
Input Validation
- PDF path validation in process.py (exists, is file, is readable)
- File size limits should be enforced at the Container App Job level
- Never trust user-provided paths without validation
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?