Add educational comments to code files to create learning resources

1. Identify the file by attaching it to the conversation or referring to it as a chat variable. If unspecified, the agent asks; if multiple files match, it lists numbered choices. 2. Optionally adjust: Comment Detail (1–3, default 2), Repetitiveness (default 2), User Knowledge for general programming knowledge (default 2), Educational Level for the specific language (default 1), Line Number Referencing for Note 1-style labels (default yes), and Nest Comments for indentation within code blocks (default yes). 3. Example: /add-educational-comments #file:output_name.py Comment Detail = 1, Repetitiveness = 1, Line Numer = no. The agent interprets the typo Line Numer as Line Number Referencing = no. 4. It plans which sections need explanations, then adds comments respecting language syntax and indentation, without emoji or special characters. 5. Review the resulting encoding and syntax. If the file has already been processed with this skill, request improvements to existing comments rather than more lines.

No accounts or external packages are required. This is textual guidance for an agent able to read and edit workspace files. Limitations: - File references such as #file: and slash commands reflect particular chat environments; attachment methods differ by agent. - Fetch List includes optional reference links, including PEP 263. Access requires web capability but is not essential. - The 125% length target is capped at 400 new lines, or about 300 lines for files exceeding 1,000 lines. - The skill edits the original file directly; review changes or use version control before accepting them. - Error-free output is not guaranteed; human review remains necessary. - License: MIT.