agentleFS
Sign inStart free
bongartzdiazbongartzdiaz/agent-skills/skills/ultrathink/SKILL.md

ultrathink

Skill0 starsChanged 10 months agoCC0-1.0View on GitHub

Display colorful ANSI art of the word "ultrathink". Use when the user says "ultrathink" or invokes /ultrathink.

6 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use fix-errors.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • gitpod-ioSkill

    fix-errors

    Guidelines for fixing unhandled errors from the VS Code error telemetry dashboard. Use when investigating error-telemetry issues with stack traces, error messages, and hit/user counts. Covers tracing data flow through call stacks, identifying producers of invalid data vs. consumers that crash, enriching error messages for telemetry diagnosis, and avoiding common anti-patterns like silently swallowing errors.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When this skill is invoked, run this Bash command to display colourful ANSI art:

    line 8
  2. Distinctive:

    Do not add any other output or commentary.

    line 14

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Ultrathink

When this skill is invoked, run this Bash command to display colourful ANSI art:

printf '\n  \033[1;31m╦ ╦\033[1;33m╦  \033[1;32m╔╦╗\033[1;36m╦═╗\033[1;34m╔═╗\033[1;35m╔╦╗\033[1;31m╦ ╦\033[1;33m╦\033[1;32m╔╗╔\033[1;36m╦╔═\033[0m\n  \033[1;31m║ ║\033[1;33m║   \033[1;32m║ \033[1;36m╠╦╝\033[1;34m╠═╣\033[1;35m ║ \033[1;31m╠═╣\033[1;33m║\033[1;32m║║║\033[1;36m╠╩╗\033[0m\n  \033[1;31m╚═╝\033[1;33m╩═╝\033[1;32m ╩ \033[1;36m╩╚═\033[1;34m╩ ╩\033[1;35m ╩ \033[1;31m╩ ╩\033[1;33m╩\033[1;32m╝╚╝\033[1;36m╩ ╩\033[0m\n\n'

Do not add any other output or commentary.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free