What problem does it solve?
Hardcoding API keys, passwords, and tokens in MATLAB scripts leaks secrets into version control and makes rotation painful. This Skill teaches agents to use the built-in MATLAB Vault (setSecret, getSecret, importSecrets, secretID) so credentials stay encrypted and out of code.
Core Features & Use Cases
- Vault lifecycle management: Store, retrieve, list, rotate, and remove secrets with setSecret, getSecret, isSecret, listSecrets, removeSecret, and metadata functions.
- Connection wiring patterns: Pass credentials into REST APIs (weboptions bearer tokens and basic auth), SFTP with passphrase-protected keys, PostgreSQL databases, and cloud storage (S3/Azure/GCS) without exposing values.
- CI and headless workflows: Use importSecrets to load dotenv files non-interactively, or getenv for runner-injected environment variables, since setSecret is interactive-only.
- Use Case: A scheduled nightly MATLAB job needs a database password and an API token. Use importSecrets to populate the vault from a secrets file, then getSecret at connect time so no plaintext credential ever appears in the script.
Quick Start
Ask your agent to refactor a MATLAB script that hardcodes an API token so it stores the token in the MATLAB Vault with setSecret and retrieves it with getSecret instead.