Reflect

Community

sharpdeveye

reflect

Analyze command history to identify which skills work, which fail, and where to improve.

Overview

Publisher	sharpdeveye
Repository	`maestro`
Skill name	`reflect`
Stars	591
Forks	73
Bundled files	Instructions only
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by sharpdeveye on GitHub. Read the source before you install it.

Installation

Install the Reflect AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/sharpdeveye/maestro/tree/main/source/skills/reflect
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/sharpdeveye/maestro.git /tmp/maestro
mkdir -p .claude/skills
cp -r /tmp/maestro/source/skills/reflect .claude/skills/reflect

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Reflect in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Reflect on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Reflect is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

MANDATORY PREPARATION

Invoke /agent-workflow — it contains workflow principles, anti-patterns, and the Context Gathering Protocol. Follow the protocol before proceeding — if no workflow context exists yet, you MUST run /teach-maestro first.

Analyze the Maestro audit trail and decision log to produce a skill-effectiveness scorecard. This tells you which commands work, which fail, and where your workflow needs attention.

Data Sources

Read these files from the project root:

.maestro/audit.jsonl — every command invocation with duration, cost, and outcome
.maestro/decisions.jsonl — decisions made with outcomes and next steps

If neither file exists, respond: "No audit data found. Run commands with Maestro to start tracking, then come back."

Analysis Dimensions

1. Usage Frequency

Which commands run most/least?
Are any commands never used? (candidates for removal)

2. Completion Rate

What % of invocations complete successfully?
Which commands fail most often?

3. Command Flow

What are the most common command sequences (A → B)?
Which commands lead to follow-ups vs. abandonment?
Abandonment rate per command (no follow-up within 30 min)

4. Cost Distribution

Total estimated cost across all commands
Cost per command (average)
Most/least expensive commands

5. Duration Analysis

Average duration per command
Outliers (unusually slow invocations)

Output Format

text
╔══════════════════════════════════════════╗
║          MAESTRO EFFECTIVENESS           ║
╠══════════════════════════════════════════╣
║ Commands Run         __ (__ unique)      ║
║ Completion Rate      __%                 ║
║ Most Used            /_____ (__×)        ║
║ Most Abandoned       /_____ (__% ⚠️)     ║
║ Avg Duration         __s                 ║
║ Total Cost           ~$__.__             ║
╠══════════════════════════════════════════╣
║           STRONGEST PIPELINES            ║
╠══════════════════════════════════════════╣
║ /_____ → /_____    __×                   ║
║ /_____ → /_____    __×                   ║
╠══════════════════════════════════════════╣
║           COST PER COMMAND               ║
╠══════════════════════════════════════════╣
║ /_____    $__.__/run  ████░░  avg        ║
║ /_____    $__.__/run  █░░░░░  cheap      ║
║ /_____    $__.__/run  █████░  costly     ║
╚══════════════════════════════════════════╝

INSIGHTS:
1. [Data-driven observation with recommended action]
2. [Data-driven observation with recommended action]
3. [Data-driven observation with recommended action]

Insights Rules

Every insight MUST:

Reference specific data (e.g., "40% abandonment rate")
Suggest a specific Maestro command to address it
Distinguish correlation from causation

Reflection Checklist

All 5 analysis dimensions covered
Scorecard generated with real data
Insights are data-driven, not speculative
Cost estimates labeled as approximate (~)
Recommended actions reference specific Maestro commands

Recommended Next Step

After reflecting, run /streamline to remove unused commands, or /refine on the most-abandoned command to improve its prompt quality.

NEVER:

Require audit data to exist — degrade gracefully
Invent metrics beyond what the logs contain
Show cost data without the "estimate" disclaimer (~)
Make judgments without evidence (say "100% completion rate" not "works great")
Compare across projects — reflect is project-scoped

Frequently asked questions

What does the Reflect AI skill do?

Analyze command history to identify which skills work, which fail, and where to improve.

Why use Reflect on TypingMind?

Because you install it once and use it with any model. Reflect is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Reflect in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/sharpdeveye/maestro/tree/main/source/skills/reflect. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Reflect?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Reflect?

As many as you like. As long as a model supports skills, you can use Reflect with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Reflect AI skill free?

Yes. It is published on GitHub by sharpdeveye under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Diagnosing Superpowers

obra

CommunityPopular

Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so…

Brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Executing Plans

Use when you have a written implementation plan to execute in a separate session with review checkpoints

Using Superpowers

Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

MANDATORY PREPARATION

Data Sources

Analysis Dimensions

Output Format

Insights Rules

Reflection Checklist

Recommended Next Step

Frequently asked questions

Related AI Skills

Set up your own AI workspace now