all-mpnet-base-v2
sentence-transformers · Kit
Turns sentences and paragraphs into 768-number vectors so you can search, cluster and compare text by meaning. It suits developers and data teams working in En…
Watches your AI sessions for corrections and repeated work, then suggests edits to your existing skills and flags candidates for new ones. You approve each change before anything is installed.
One Skill to Rule Them All (task-observer) is an open-source project on GitHub in the Productivity category, listed by Mindket. It is free. This is version 1, last updated on . Install it from GitHub as its README says. Get Mindket’s setup notes on your Mindket account, as a zip.
npx skills add rebelytics/one-skill-to-rule-them-all --skill task-observer
task-observer is a meta-skill that runs alongside your other skills and watches how they perform. When you do the same job manually again and again, it points that out as something a new skill could take over. It also notes corrections you make and suggests specific edits to skills you already have.
People who build and keep a library of AI skills and want it to improve from real use instead of staying frozen. It also suits anyone who keeps correcting the same thing in their agent output.
| Industry | Who uses it | How they use it | Example |
|---|---|---|---|
| Consulting | Knowledge workers with many repeatable tasks | Let it flag recurring work as skill candidates and help build them | A report format you keep fixing by hand |
| Software | Developers who write skills for coding agents | Review its suggested edits to tighten skill instructions | A skill that triggers in the wrong places |
| Content | Writers and editors with house style rules | Turn repeated style corrections into updates of a writing skill | A tone fix you have made in several drafts |
| Operations | Teams that share a skill library | Use its cross-cutting principles log to keep quality steady across skills | A rule that should apply to every new skill |
Anyone with only a skill or two, or who does not mind writing skill updates by hand, can skip it.
It installs as a skill, so it runs wherever your skills load.
| Use case | Who | What they get back |
|---|---|---|
| Find a new skill | Anyone repeating manual work | A flagged pattern and help turning it into a skill |
| Improve a skill | Skill owners | Specific update suggestions based on corrections and gaps |
| Raise the quality floor | Library maintainers | New skills checked against shared cross-cutting principles |
You need a place that loads skills, and Node.js if you use the terminal route. Installing is only half the job, because the skill must also be switched on.
npx skills add rebelytics/one-skill-to-rule-them-all --skill task-observer
Adding the -g option installs it for all your projects instead of one.
Work as you normally do. The skill runs in the background of each session and writes down what it notices. You read the observations and decide which ones become changes.
| Tool | What it does |
|---|---|
| Observation log | One entry per observation, with the skills it touches and a proposed fix |
| Cross-cutting principles log | Holds patterns that apply to many skills, and new skills are checked against them |
| Staged copies | Where scheduled reviews put changes that need no decision from you |
You correct an agent three times because its weekly summary keeps the wrong tone. The observer logs that as a signal, names the summary skill as affected and proposes a specific edit. You approve it, then install the updated bundle.
If you are new, install it, switch it on, then work as usual for a few sessions. Read the observations it writes and approve one small change to see the cycle.
If you know the field, the point is the gap between project memory and a reusable skill. Project memory stores a fact for one project and applies it as an instruction. An observation here is a proposal that reaches every project loading the skill, and a human review sits in between.
# One Skill to Rule Them All (task-observer) Watches your AI sessions for corrections and repeated work, then suggests edits to your existing skills and flags candidates for new ones. You approve each change before anything is installed. Made by rebelytics on GitHub. These notes are Mindket's, written from its README; the project's own files and license are in its repository. ## About What it is: task-observer is a meta-skill that runs alongside your other skills and watches how they perform. When you do the same job manually again and again, it points that out as something a new skill could take over. It also notes corrections you make and suggests specific edits to skills you already have. Who it suits: People who build and keep a library of AI skills and want it to improve from real use instead of staying frozen. It also suits anyone who keeps correcting the same thing in their agent output. ```table Industry | Who uses it | How they use it | Example Consulting | Knowledge workers with many repeatable tasks | Let it flag recurring work as skill candidates and help build them | A report format you keep fixing by hand Software | Developers who write skills for coding agents | Review its suggested edits to tighten skill instructions | A skill that triggers in the wrong places Content | Writers and editors with house style rules | Turn repeated style corrections into updates of a writing skill | A tone fix you have made in several drafts Operations | Teams that share a skill library | Use its cross-cutting principles log to keep quality steady across skills | A rule that should apply to every new skill ``` Anyone with only a skill or two, or who does not mind writing skill updates by hand, can skip it. Where to use it: It installs as a skill, so it runs wherever your skills load. - Agents and tools reached by the skills command line tool, such as Claude Code - The Claude apps: web, desktop, mobile and Cowork, through an uploaded skill bundle - Hermes and Openclaw setups, which users report working too ```table Title: What it does for you Use case | Who | What they get back Find a new skill | Anyone repeating manual work | A flagged pattern and help turning it into a skill Improve a skill | Skill owners | Specific update suggestions based on corrections and gaps Raise the quality floor | Library maintainers | New skills checked against shared cross-cutting principles ``` How to set it up: You need a place that loads skills, and Node.js if you use the terminal route. Installing is only half the job, because the skill must also be switched on. - Node.js, for the skills command line tool - A CLAUDE.md file or your platform equivalent, to hold the activation instruction 1. Run the terminal command below. In the Claude apps, upload the .skill file from the newest release in the settings instead. 2. Copy the activation instruction found in references/environments.md into your CLAUDE.md, or the matching file on your platform. 3. Check that it runs, using the check described in the project documentation. ```bash npx skills add rebelytics/one-skill-to-rule-them-all --skill task-observer ``` Adding the -g option installs it for all your projects instead of one. How to use it: Work as you normally do. The skill runs in the background of each session and writes down what it notices. You read the observations and decide which ones become changes. ```table Title: What it produces Tool | What it does Observation log | One entry per observation, with the skills it touches and a proposed fix Cross-cutting principles log | Holds patterns that apply to many skills, and new skills are checked against them Staged copies | Where scheduled reviews put changes that need no decision from you ``` Example: You correct an agent three times because its weekly summary keeps the wrong tone. The observer logs that as a signal, names the summary skill as affected and proposes a specific edit. You approve it, then install the updated bundle. For newcomers and experts: If you are new, install it, switch it on, then work as usual for a few sessions. Read the observations it writes and approve one small change to see the cycle. If you know the field, the point is the gap between project memory and a reusable skill. Project memory stores a fact for one project and applies it as an instruction. An observation here is a proposal that reaches every project loading the skill, and a human review sits in between. ```flow You work and correct the agent Observer logs corrections and gaps It suggests skill changes You review and approve You install the updated bundle ``` Good to know: - License: CC-BY-4.0. - Your installed skills are left as they are, and changes take effect only once you install the new bundle. - Scheduled reviews only apply no-decision changes to staged copies. - The skill description alone tends to under-trigger, so the activation instruction is needed. - The author reports more than 2,300 logged observations across their own 87 skills. - The project credits over 100 contributors and reports over 17,000 installs on the skills.sh listing. ## On GitHub, 16 November 2026 - Stars: 3,924 - Forks: 390 - Watching: 13 - Open issues and pull requests: 33 - Language: Markdown - License: CC-BY-4.0 - Topics: agent-skills, ai-skills, augmented-expertise, awesome-skills, claude, claude-code, claude-code-skill, claude-code-skills, claude-cowork, claude-skills, meta-skill, rebelytics ## Links - Code: https://github.com/rebelytics/one-skill-to-rule-them-all - Website: https://www.rebelytics.com/task-observer/ - Releases: https://github.com/rebelytics/one-skill-to-rule-them-all/releases - Issues: https://github.com/rebelytics/one-skill-to-rule-them-all/issues - Star history: https://www.star-history.com/#rebelytics/one-skill-to-rule-them-all&Date ## Get the code ``` git clone https://github.com/rebelytics/one-skill-to-rule-them-all.git ``` Then follow the setup in its README. Nothing in this kit runs by itself.
README.md 6 KB
Listed GitHub projects in the same category that share the most topics with this one.
| Product | Stars | Activity | Language | License | Last change |
|---|---|---|---|---|---|
| One Skill to Rule Them All (task-observer) This page | 3,927 | Active | Markdown | CC-BY-4.0 | |
| AIEVShares claude-skills · claude · claude-code | 124 | Active | TypeScript | MIT | |
| Frontend SlidesShares claude · claude-code | 32,301 | Quiet | JavaScript | MIT |
Posts and comments that name this project on Hacker News, Bluesky, X, Reddit, Facebook and YouTube, found by a weekly search and on Trendshift. Mindket doesn’t write or check them. Open one to read it where it was posted.
sentence-transformers · Kit
Turns sentences and paragraphs into 768-number vectors so you can search, cluster and compare text by meaning. It suits developers and data teams working in En…
intfloat · Kit
Turns text in about 100 languages into vectors so you can compare meaning across them, for search and matching. Made for developers who build multilingual retr…
aldegad · Skill
Turns one base drawing of a character into game-ready sprites, either an atlas with a manifest or transparent motion loops, for game developers working in Code…
michael-denyer · Skill
Michael Denyer’s port of Lauren Tan’s pstack skill stack to Claude Code, Codex, Pi, GitHub Copilot, Muse and other agents. Tell its poteto-mode skill your goal…
coreyhaines31 · Skill
A set of marketing skills for coding agents, covering conversion, copywriting, SEO, analytics and growth. Built for technical marketers and founders who use Cl…
wshobson · Skill
Offers a catalog of plugins that bundle agents, skills and commands for AI coding tools including Claude Code, Codex CLI, Cursor and GitHub Copilot, kept as on…