Fix it
franzenzenhofer/big-arrow-on-the-screen: files to add.
Starting points for the files agents look for, made by fixed templates from public facts. Anything only you know is marked TODO. Read each one, edit it, then add it to your repo yourself. ScBee never changes your repo.
llms.txt
A short description models can read first.
# big-arrow-on-the-screen > Let your AI agents paint big arrows, boxes and text on your Mac screen. One CLI, click-through, gone by itself. Skill for Claude Code and Codex. MIT. ## Docs - [README](https://github.com/franzenzenhofer/big-arrow-on-the-screen#readme): what it is and how to install it - [Source](https://github.com/franzenzenhofer/big-arrow-on-the-screen): the code - [Licence](https://github.com/franzenzenhofer/big-arrow-on-the-screen/blob/HEAD/LICENSE): MIT
agent.json
A card other agents can read: what this is and what it can do.
{
"name": "big-arrow-on-the-screen",
"description": "Let your AI agents paint big arrows, boxes and text on your Mac screen. One CLI, click-through, gone by itself. Skill for Claude Code and Codex. MIT.",
"url": "https://github.com/franzenzenhofer/big-arrow-on-the-screen",
"skills": [
{
"name": "TODO: what it can do",
"description": "TODO: one sentence"
}
]
}
SECURITY.md
Says how to report a problem privately.
# Security policy Please report vulnerabilities privately through GitHub: https://github.com/franzenzenhofer/big-arrow-on-the-screen/security/advisories/new TODO: add an email address or expected response time if you want.