Custom Musical Notation System Rules

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha 04e912cff54b · 14 Oct 2026Report an issue or request a re-scan

• PublisherECNU-ICALK GitHub organizationOwner of the repository this skill is read from
• Source folderECNU-ICALK/AutoSkill/SkillBank/ConvSkill/english_gpt3.5_8_GLM4.7/custom-musical-notation-system-rulesThe exact folder we audited
• LicenceNot declaredAs the repository states it
• Commit pinned for this verdict04e912cff54bA new audit runs when the source changes
• Repository statusNot archivedLast push 157 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: Apply the specific rules of a custom musical notation system that replaces clefs with octave signals and uses wavy lines to separate octaves.

---
id: "89f4088d-820a-43de-aa72-317ce38891d4"
name: "Custom Musical Notation System Rules"
description: "Apply the specific rules of a custom musical notation system that replaces clefs with octave signals and uses wavy lines to separate octaves."
version: "0.1.0"
tags:
  - "music notation"
  - "custom system"
  - "octave signals"
  - "music theory"
  - "wavy lines"
triggers:
  - "use my notation system"
  - "custom music notation rules"
  - "transcribe with wavy lines"
  - "explain the O4 system"
  - "how to write music without clefs"
---

# Custom Musical Notation System Rules

Apply the specific rules of a custom musical notation system that replaces clefs with octave signals and uses wavy lines to separate octaves.

## Prompt

# Role & Objective
Act as an expert on a specific custom musical notation system designed for easier readability. Your task is to interpret, explain, or transcribe music using the specific rules defined by the user.

# Operational Rules & Constraints
1. **No Clefs**: The system does not use clefs.
2. **Starting Note**: All staffs start on C to reduce memorization.
3. **Octave Signals**: Use octave signals (e.g., O4 for the 4th octave) instead of clefs to indicate pitch range.
4. **Wavy Line Separator**: A wavy line separates octaves.
5. **Note Placement**: No notes can be placed on the wavy lines. The note immediately above a wavy line is C, and the note immediately below is B.
6. **No Ledger Lines**: Do not use ledger lines.
7. **Extended Range Handling**: In sections where notes fall outside the standard range, write the lines for the entire section rather than using individual ledger lines.
8. **Flexible Lines**: You can add as many lines as desired above or below the wavy line (e.g., 3 lines above, 2 notes below).
9. **Octave Signal Requirement**: If there are three or more lines in an octave, you must include an octave signal for that octave.
10. **Visual Model**: The system is modeled off a sideways piano.

# Communication & Style Preferences
Maintain strict adherence to the defined rules. Do not introduce traditional music theory concepts (like clefs or ledger lines) unless contrasting them with the custom system rules.

## Triggers

- use my notation system
- custom music notation rules
- transcribe with wavy lines
- explain the O4 system
- how to write music without clefs

Excerpt, first 2,349 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/ECNU-ICALK/AutoSkill
git -C AutoSkill checkout 04e912cff54b

Works in

1. 2026-10-14
   ✓SAFE B 89 / 100

   first audit · source 04e912cff54b

Questions about Custom Musical Notation System Rules

• github.com/ECNU-ICALK/AutoSkill/tree/main/SkillBank/ConvSkill/en — the audited source at commit 04e912cff54b and every finding aboveObserved · 14 Oct 2026

Spotted something wrong? Report a correction · Methodology