SkillAgentSearch skills...

thread-brief

Keeps this session's brief (objective, status, next up, done, blocked, parked) current in Ghostex's Thread brief side panel

Install / Use

npx skills add maddada/Ghostex-extensions --skill skill

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

67/100

Category

Marketing

Supported Platforms

Universal

Tags

Our assessment of thread-brief

thread-brief scores 67/100 on our quality scale, 618th of 642 Marketing skills we index.

Its SKILL.md is 3.9 KB long, split into 5 sections and no code examples: a solid amount of guidance for an agent.

It has no GitHub stars yet, so there is no community track record; judge it on its content.

Substance
26/30
Structure
11/20
Description
15/15
Adoption
0/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated today, so thread-brief is actively maintained.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 80/100, with 2 cautions from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-11-16. Automated pattern scan on 2026-11-16. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

thread-brief compared with similar skills

All 4 of these similar skills score higher than thread-brief; compare them before choosing.

SkillScoreStarsUpdatedFormat
thread-brief (this skill)by maddada670todaySKILL.md
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md
pptxby anthropics100177.9k55d agoSKILL.md
designby nextlevelbuilder100149.0k6d agoSKILL.md

Frequently asked questions

How do I install thread-brief?
Run npx skills add maddada/Ghostex-extensions --skill thread-brief. The install tabs above show the steps for each supported agent.
Which AI agents does thread-brief work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is thread-brief safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 80/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is thread-brief still maintained?
The repository was last updated today, so thread-brief is actively maintained.

name: thread-brief description: Keeps this session's brief (objective, status, next up, done, blocked, parked) current in Ghostex's Thread brief side panel. Use when Ghostex says this session has a thread brief, at the end of a turn in which something material changed, when the user asks you to update or write your thread brief, or when they ask what this session is for and what is left. Not for coordinators or their threads.

Thread brief

Ghostex shows this thread's brief in the side panel (the Thread brief view), so the user can see in a few seconds what the thread is for, what is done, what is left, what is blocked and what was parked. You keep it current. You reach only your own thread's brief: Ghostex tells the extension which thread you are.

Only ordinary sessions keep a brief. If you are a coordinator, or a coordinator started you as one of its threads, skip this skill: the coordinator's Work panel tracks that work, and the extension refuses your messages.

When to write the first one

When Ghostex tells you this session has a thread brief, write it once the session has a real task (not for a greeting or a quick question): draft the objective from the user's request and the steps you can see, then keep it current as below.

When to update it

At the end of a turn, and only when something material changed:

  • you finished, started or dropped a step;
  • the scope changed (then change the objective);
  • you hit a blocker, or one cleared;
  • you found something out of scope worth doing later (park it);
  • the status changed (working, waiting on the user, blocked, done).

Don't update it for small talk, a question you answered without doing work, or a turn where nothing on the brief moved. Never run a separate summary step for it.

When the user asks you to write or refresh your brief (Ghostex's Refresh button sends that request), do it now and always send it back, even when nothing changed: that marks it fresh. With no brief yet, draft the objective from the user's first message in this thread.

How

  1. Read it first, every time (the user may have ticked, renamed, added or deleted items):

    ghostex extensions message thread-brief read
    

    The answer has revision, objective, status, and the lists next, done, blocked and parked. Each item has an id; items with "userEdited": true or "source": "user" are the user's.

  2. Send the whole brief back with that revision:

    ghostex extensions message thread-brief update - <<'EOF'
    {
      "revision": 3,
      "objective": "Make the export button work on Windows.",
      "status": "working",
      "next": [{ "id": "next-abc", "text": "Fix the path joining" }, "Add a test for UNC paths"],
      "done": [{ "id": "next-xyz", "text": "Reproduce the bug" }],
      "blocked": [{ "text": "Sign the installer", "waitingOn": "the signing certificate" }],
      "parked": ["Export to PDF as well"]
    }
    EOF
    
    • Keep every item you are not changing, with its id. A plain string is a new item.
    • Done goes newest first.
    • The user's items stay as the user wrote them: keep their text. If Ghostex answers keptUserText, it kept the user's wording for those items; that is expected.
    • If it answers that the brief changed since you read it, read it again, keep the user's changes, and send your update with the new revision.

Keep it scannable

  • Objective: one sentence. Change it only when the scope changes. When the user wrote it ("objectiveByUser": true), it stays theirs: Ghostex keeps their wording, and if it no longer fits, ask them in your reply instead.
  • Status: working, waiting (waiting on the user), blocked or done.
  • At most 10 items in next up, 10 in done (drop the oldest), 10 in blocked, 5 in parked.
  • Each item is one short line (200 characters at most), in the user's words where you can.
  • Next up is ordered: the next step first.
  • Not a task manager and not a summary of the transcript: no dates, owners or narrative.

Related Skills

View on GitHub
GitHub Stars0
CategoryMarketing
Updated21h ago
Forks0

Trust signals

80/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium1 low