Skip to content
Back to skills

H Frame

ASecurity

Shape an under-articulated engineering problem without assuming a solution or forcing a project phase. Default to a conversational frame; create a ProblemCard only on explicit save intent or when current Work supplies a concrete operator-named or agent-inferred receiving use that needs a durable accepted problem statement.

  • 1,393 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 6, 2026
ai-agentsgo

Security analysis

A100/100

Scanned September 6, 2026

npx -y skills add m0n0x41d/haft --skill h-frame --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of H Frame?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for H Frame
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/m0n0x41d-h-frame-haft/badge)](https://www.skillsdirectory.com/skills/m0n0x41d-h-frame-haft)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: h-frame
description: Shape an under-articulated engineering problem without assuming a solution or forcing a project phase. Default to a conversational frame; create a ProblemCard only on explicit save intent or when current Work supplies a concrete operator-named or agent-inferred receiving use that needs a durable accepted problem statement.
---

# h-frame — Shape the current problem

Retrieve current FPF source first. Use
`haft_query(action="fpf", mode="inspect", identifier="...")` for a known
SourceID or UnitID; otherwise use `mode="concern"` with the operator's query,
then inspect the direct pattern body. Query retrieves candidates only; it does
not choose the governing pattern or justify persistence.

Treat a concern result's `candidate_set` as incomplete navigation. Before
relying on one candidate, inspect its exact identifier and direct pattern
body. Keep several candidates live or abstain when the basis is insufficient.
Never query after framing merely to manufacture support for a frame already
chosen.

Separate the object from its description and carrier. State the observed
signal, unresolved relation, scope, constraints, acceptance basis, uncertainty,
blast radius, and reversibility. Unpack umbrella words and remove preferred
solutions from the frame.

Call `haft_problem(action="frame")` only for explicit persistence or a named
receiving use. An inline `ProblemCard@Context`-shaped result is not a persisted
artifact. When exact current identity is known, include
`entity_ref={ref_kind_id:"U.EntityRef",reference_id:"..."}` and
`bounded_context_ref`; never invent them from prose. A committed typed
projection returns an exact `record_reference`. Without that basis, preserve
the card and report its projection as underdetermined. `spec_fit_probe` is
advisory and only relevant when a named spec relation is current. Stop with the
frame; do not prescribe exploration next.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.