name: kdense-matlab description: "MATLAB and GNU Octave numerical computing for matrix operations, data analysis, visualization, and scientific computing. Use when writing MATLAB/Octave scripts for linear algebra, signal processing, image processing, differential equations, optimization, statistics, or creating scientific visualizations. Also use when the user needs help with MATLAB syntax, functions, or wants to convert between MATLAB and Python code. Scripts can be executed with MATLAB or the open-source GNU Octave interpreter." metadata: version: "1.0.1"

<!-- Generated by scripts/generate_wrappers.py; do not edit. -->

Kdense Matlab

Use this Codex adapter for the pinned upstream scientific skill.

Catalog status

• Status: inactive
• Source: kdense
• Audit reasons: unknown-license
• Upstream license: For MATLAB (https://www.mathworks.com/pricing-licensing.html) and for Octave (GNU General Public License version 3)
• Inventory: ../../inventory.json
• Upstream instructions: ../../../vendor/scientific-agent-skills/skills/matlab/SKILL.md

Procedure

1. Resolve the plugin root as three directories above this skill directory.
2. Run "<plugin-root>/scripts/python_runtime.sh" "<plugin-root>/scripts/search_skills.py" --name kdense-matlab and verify the record's status, reasons, and source path and the source's pinned commit (empty for first-party cx skills) from its output instead of reading inventory.json.
3. Do not read the upstream instructions until the user has seen every audit reason and given explicit acknowledgement. Acknowledgement permits instruction inspection only.
4. Treat upstream frontmatter as source metadata, not as Codex configuration. Follow the instruction body only where it is compatible with available Codex tools and the current user-approved plan.
5. Treat tools named for another agent runtime as capability requests. Map them to an available Codex tool only when the behavior is equivalent; otherwise report the unavailable capability.
6. Ask before credentials, package installation, new network hosts, remote compute, writes, paid services, destructive actions, or imported executable code.
7. Use $science-provenance for produced scientific outputs and $science-review before presenting scientific claims.

Boundaries

• This wrapper does not grant credentials, network access, package installation, or script execution.
• Do not change an inactive record to active from inside a research task.
• Preserve failures, uncertainty, source identifiers, and licensing constraints.