degreesign
Skill1 starsChanged 18 days agoMITView on GitHub
Route a task to the right DegreeSign sub-skill and keep the installed collection current. Use when a task needs Material Symbols icons, an npm package release or architecture map, the house coding conventions, a TypeScript web app structure, a Node backend structure, task backlog management or LLM discovery files, or when asked to check for updates to the installed skills.
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
Read the matching file before acting.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
DegreeSign
One entry skill for the DegreeSign collection. It routes a task to the matching sub-skill and checks for a newer published version at most once a day.
When to use
- A task matches one of the sub-skills below.
- You need to know which sub-skill applies.
- You need to check whether the installed collection is current.
Sub-skills
Read the matching file before acting. Resolve each path relative to this SKILL.md.
skills/icons/SKILL.md: add, find, audit and rasterize Material Symbols Rounded icons.skills/npm/SKILL.md: release and maintain an npm package, including its architecture map.skills/coding/SKILL.md: apply the house coding conventions when editing a repository.skills/webapp/SKILL.md: structure or restructure a TypeScript web app.skills/server/SKILL.md: structure or restructure a Node backend.skills/todo/SKILL.md: manage a project's task backlog and ticket file.skills/llms/SKILL.md: publish, audit and fixllms.txtand Markdown page versions.
Load only the sub-skill a task needs; do not read every sub-skill up front.
Keep the collection current
At the start of a session, run the bundled check once per machine per day. Run node on the check.mjs that sits beside this SKILL.md, using its absolute path.
The check reads the install marker, queries the npm registry at most once every 24 hours (the result is cached under the XDG cache directory so every session on the machine shares one timestamp), and prints an update command when a newer version exists. When it reports a newer version, ask the user whether to update, then run the printed command. Never update without asking.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.