A skill for AI assistants

The answer first.
Not the long way around.

Depth when it helps.

Progressive Clarity guides your assistant to lead with the answer, keep important caveats beside it, and add detail that earns its place. Follow-ups stay focused—not another essay.

Free & open source · No separate account · Your existing AI app

The practical difference

Don’t bury what changes the answer.

Same facts. Different order. Someone who stops reading early should still get the important boundary.

A buried qualification

“Yes, enable it. The checks passed, and rollback is available. … This applies only to staging; production is not approved.”

The opening says yes. The boundary arrives later.

Answer first, scope included

“Enable it in staging only. Validation and rollback checks passed; production has not been approved.”

The recommendation and its limit travel together.

Illustrative writing comparison—not a model benchmark or a claim that every unconfigured assistant responds this way.

See it work

One conversation.
The right amount of detail.

A quick answer. A plan with useful depth. A focused follow-up. The format changes with the question—not just the topic.

Pick an example

Everyday

Keeping your family photos safe

  1. 01 Focused Quick question
    You

    Is cloud photo sync the same as a backup?

    Assistant

    Not necessarily. Sync keeps one library matched across devices, so deletions and unwanted changes can spread. A backup is a separate copy you can restore.

  2. 02 Full More to consider
    You

    My cloud library holds years of family photos. Should it be the only copy? Recommend a backup setup I can rely on.

    Assistant

    At a glance

    No. Keep at least one independent backup that survives accidental deletion, account lockout, or failure of the synced library.

    In context

    Sync helps when a device is lost, but it is designed to mirror changes—not preserve every past state. Deleting the wrong folder or losing account access can remove the recovery path you thought you had.

    At depth

    Keep the live library plus a local backup and a second off-site or versioned copy. Automate both, protect recovery credentials, and test restoring a few photos before trusting the setup.

  3. 03 Focused Follow-up
    You

    My library is 280 GB and grows by 3 GB a month. What capacity covers three years plus 25% headroom?

    Assistant

    You need about 485 GB of usable space: (280 + 3 × 36) × 1.25. A 1 TB drive is the practical choice once formatting, version history, and continued growth are included.

Developer

Keeping payment records reliable

  1. 01 Focused Quick question
    You

    Is Redis a database?

    Assistant

    Yes. Redis is an in-memory data store that can persist data, but its durability depends on how it is configured.

  2. 02 Full More to consider
    You

    We process card payments. Should Redis be our sole source of truth for payment state?

    Assistant

    At a glance

    No. Keep canonical payment state in transactional storage with tested recovery, and use Redis only for roles where data loss is recoverable.

    In context

    Payment updates often span status, money movement, idempotency, and audit history. A transactional database can commit related changes together; explicit transition records preserve what happened and when.

    At depth

    Redis can still accelerate reads, coordinate short-lived work, and hold idempotency keys. Design cache loss as recoverable, bound lock lifetimes, and test replay, failover, stale reads, and delayed webhooks before production use.

  3. 03 Focused Follow-up
    You

    Our provider retries webhooks for up to 72 hours, and we require a 24-hour buffer. What TTL should the idempotency keys use?

    Assistant

    Use a 96-hour TTL. That covers the 72-hour retry window plus the required 24-hour buffer.

Crypto broker

Controlling execution risk

  1. 01 Focused Quick question
    You

    What does slippage mean in a trade?

    Assistant

    Slippage is the difference between the expected execution price and the average price actually received. It usually grows when an order is large relative to available liquidity.

  2. 02 Full More to consider
    You

    A client wants to buy $750,000 of a thinly traded token. Only $220,000 is offered within 1% of the current price. Should I send one market order?

    Assistant

    At a glance

    No. The order is more than three times the visible depth, and a market order leaves price impact uncapped. Use an approved execution plan with a hard slippage limit.

    In context

    The top quote represents only the next fill, not the average for the whole order. Consuming the book can move later fills sharply, while fragmented venues, fees, and latency can widen the realized cost.

    At depth

    Confirm the client mandate and venue limits, then compare staged limit orders, approved liquidity providers, and venue splitting. Define the benchmark, time window, cancellation rule, and post-trade review before routing.

  3. 03 Focused Follow-up
    You

    The client allows 60 basis points. Expected impact is 42 bps and fees are 8 bps. Are we inside the limit?

    Assistant

    Yes—50 bps total, leaving 10 bps of headroom. That assumes both estimates use the same notional and no other execution costs apply.

These conversations are written examples, not live AI output. The broker scenario is educational, not investment or execution advice.

How it works

Not a three-section template for every answer.

Most questions need a focused answer. Use three views only when the answer, reasoning, and practical detail each add something useful.

Focused

A direct, complete answer.

For quick facts, follow-ups, and decisions that can be explained simply. Just the answer and the context you need to use it.

Full

Three views, each worth reading.

  1. At a glance — the answer and any caveat that changes what it means for you.
  2. In context — why it makes sense, what matters, and what to do next.
  3. At depth — evidence, alternatives, or practical details when you want to dig in.

The skill guides your assistant's responses. It can't guarantee activation, accuracy, or consistency across chats. Live-app behavior hasn't been verified.

Install

Your assistant. A clearer way to answer.

Choose your app, follow its setup steps, then try a question you care about. Downloads are package 0.5.1; directory listings update separately.

01

Chat apps

Package 0.5.1

ChatGPT

Open the published plugin listing in ChatGPT. The listing may be an older approved release; the ZIP is a separate download.

Setup & availability
  1. Open the plugin listing using the button below.
  2. If your account supports plugins, follow the listing’s installation flow.
  3. Start a new chat with the plugin enabled and try a prompt below.

Confirm: Check the installed version in ChatGPT. Access depends on your account; downloading a ZIP does not install it.

Package 0.5.1

Claude.ai

Add Progressive Clarity as a custom Skill in Claude.

Setup steps
  1. Download the Claude.ai Skill.
  2. Enable code execution, then open Customize → Skills.
  3. Choose Add, upload the ZIP, and enable the Skill.

Confirm: It is enabled in Customize → Skills, then try a prompt below.

02

Coding tools

Available 0.5.1

Claude Code

Install from the project’s repository marketplace, then invoke the skill in a Claude Code session.

Setup commands
  1. Run these commands in a terminal:
claude plugin marketplace add firaskafri/progressive-clarity
claude plugin install progressive-clarity@firas-kafri-plugins
  1. Start a new Claude Code session.
  2. Run /progressive-clarity and ask a question.

Confirm: claude plugin list reports version 0.5.1.

Package 0.5.1

Cursor

Add the skill to one project or use it across projects.

Setup steps
  1. Download and extract the Cursor Skill.
  2. For this project, put the progressive-clarity folder in .cursor/skills/.

For all projects, use ~/.cursor/skills/. Shared agent locations .agents/skills/ and ~/.agents/skills/ are alternatives—not additional steps.

  1. Open Cursor in that project and start a new Agent chat.

Confirm: Type /, search for Progressive Clarity, and select it for one message.

Platform names and marks belong to their respective owners.

Your first chat

Try it. Then ask a follow-up.

Use these in your assistant after setup. Look for the answer up front, genuinely new detail, and no unnecessary recap.

Suggested: Focused A quick question
Is cloud photo sync the same as a backup?
Suggested: Full A bigger decision
My cloud library holds years of family photos. Should it be the only copy? Recommend a backup setup I can rely on.

Have a preference? Just ask.

  • Keep it brief.
  • No headings.
  • Answer in Focused format.
  • Use Full format with all three views.

More examples

Clear answers start with good judgment.

Ask when a key detail is missing. Correct mistakes plainly. Respect the format you asked for.

These are written examples, not live AI output.

Principles

What the skill asks your assistant to do.

Read the six writing principles
  1. 01

    Make every word count

    Use as much detail as the question needs, even when the answer is short.

  2. 02

    Add something new

    Each section should help you understand more, not repeat the last one.

  3. 03

    Ask what matters

    Ask for missing details that would actually change the answer.

  4. 04

    Show the assumptions

    Keep assumptions beside the advice, especially when numbers are involved.

  5. 05

    Fix mistakes plainly

    Say what was wrong, what's right, and what changes because of it.

  6. 06

    Keep the work usable

    Let code be code, stories be stories, and step-by-step guides stay complete.

Ready to try it?

Less digging.
More understanding.

Keep using your assistant. Give it a clearer set of instructions for the way it answers.