apple-notes-writer
Analysis
The skill matches its Apple Notes purpose, but needs review because it can read/modify iCloud Notes and builds AppleScript commands from insufficiently escaped folder/account inputs.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
parser.add_argument('--folder', default='Notes', help='Target folder') ... set targetFolder to folder "{folder}" of targetAccount ... subprocess.run(['osascript', '-e', script], ...)The folder value is exposed as a CLI/API parameter, interpolated directly into an AppleScript string, and then executed with osascript. Unlike title/body, folder/account fields are not passed through _escape_for_applescript.
Source: unknown; Homepage: none; OS restriction: none; Required binaries: none; Install specifications: No install spec
The registry metadata does not declare the macOS/Apple Notes/osascript runtime expectations, even though the skill documentation and implementation rely on them.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
def __init__(self, account: str = "iCloud") ... set body of targetNote to noteBody ... return body of targetNote
The skill uses the locally signed-in iCloud Notes account to write/update notes and to read note bodies. This is expected for an Apple Notes writer, but it is sensitive account access.