How do I install the Consult Frame skill?

Run npx skillmds@latest add timelnapp/consult-frame in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Consult Frame safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Consult Frame?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Consult Frame free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Consult Frame?

Timelnapp (@timelnapp) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Consult Frame by timelnapp — Agent Skill

Name: Consult Frame
Author: Timelnapp

Consult Frame

Trigger on "frame the engagement", "consult frame", "problem frame", "scope card", "definition of good", "what decision does this support", "in scope out of scope", "client brief → frame", "one-pager frame". Turns a brief or transcript into a structured engagement frame. NOT the solution arc (use consult-arc), NOT phasing gates (use consult-gates), NOT memory recall (use timeln-find / timeln-decided).

Timelnapp 03278af 2.4 KB Updated Sep 17, 2026

File contents

Consult Frame -- Engagement Frame Card

Turn raw client input into one structured frame: decision, success definition, scope boundaries, stakeholders.

Inputs

Input	Required	Notes
Brief, transcript, bullets, or notes	yes	Paste as-is if no file
Client / industry labels	if known	For naming only

Optional prefetch (user may ask): timeln-find / timeln-decided for prior domain or settled calls -- cite titles only when using Timeln output.

Workflow

Extract the decision the work supports (buy/build, fund phase, vendor pick, go/no-go, etc.). If multiple, pick the primary; list secondaries one line each.
Write definition of good -- observable outcome the client wants, not activity.
List in scope / out of scope as explicit bullets; flag assumptions that must hold or the frame is wrong.
Name stakeholders: decision owner, working team, approvers, blockers if mentioned.
Record open questions that block a firm frame (max 5).

Output -- exactly this shape

## Frame -- <client or "TBD"> -- <YYYY-MM-DD>

**Primary decision:** <one sentence>

**Definition of good:** <one sentence>

**In scope**
- ...

**Out of scope**
- ...

**Assumptions**
- ...

**Stakeholders**
| Role | Name / team | Notes |
|---|---|---|
| Decision owner | |
| Delivery / working team | |
| Other | |

**Open questions**
1. ...

Rules

Do not write MVP/roadmap/phasing here -- frame only.
If the source is silent on a section, write unknown -- confirm instead of inventing.
One primary decision per card unless the source explicitly ties multiple decisions at the same level.

Common failure modes

Mistake	Fix
Bulleted features instead of "good"	Rewrite as outcome the exec would recognize as done
Scope creep in "good"	Move extra work to in-scope bullets or out-of-scope
Stakeholder = generic "business"	Replace with named role or `unknown -- confirm`

---name: consult-framedescription: Trigger on "frame the engagement", "consult frame", "problem frame", "scope card", "definition of good", "what decision does this support", "in scope out of scope", "client brief → frame", "one-pager frame". Turns a brief or transcript into a structured engagement frame. NOT the solution arc (use consult-arc), NOT phasing gates (use consult-gates), NOT memory recall (use timeln-find / timeln-decided).license: MIT---# Consult Frame -- Engagement Frame CardTurn raw client input into one structured frame: decision, success definition, scope boundaries, stakeholders.## Inputs| Input | Required | Notes ||---|---|---|| Brief, transcript, bullets, or notes | yes | Paste as-is if no file || Client / industry labels | if known | For naming only |Optional prefetch (user may ask): `timeln-find` / `timeln-decided` for prior domain or settled calls -- cite titles only when using Timeln output.## Workflow1. Extract the **decision** the work supports (buy/build, fund phase, vendor pick, go/no-go, etc.). If multiple, pick the **primary**; list secondaries one line each.2. Write **definition of good** -- observable outcome the client wants, not activity.3. List **in scope** / **out of scope** as explicit bullets; flag **assumptions** that must hold or the frame is wrong.4. Name **stakeholders**: decision owner, working team, approvers, blockers if mentioned.5. Record **open questions** that block a firm frame (max 5).## Output -- exactly this shape```## Frame -- <client or "TBD"> -- <YYYY-MM-DD>**Primary decision:** <one sentence>**Definition of good:** <one sentence>**In scope**- ...**Out of scope**- ...**Assumptions**- ...**Stakeholders**| Role | Name / team | Notes ||---|---|---|| Decision owner | || Delivery / working team | || Other | |**Open questions**1. ...```## Rules- Do not write MVP/roadmap/phasing here -- frame only.- If the source is silent on a section, write `unknown -- confirm` instead of inventing.- One primary decision per card unless the source explicitly ties multiple decisions at the same level.## Common failure modes| Mistake | Fix ||---|---|| Bulleted features instead of "good" | Rewrite as outcome the exec would recognize as done || Scope creep in "good" | Move extra work to in-scope bullets or out-of-scope || Stakeholder = generic "business" | Replace with named role or `unknown -- confirm` |

Frequently asked questions