# Hipson Adapter

> Use this skill for lightweight Hipson-style research maps, internet mapping packets, bounded instruction packets, review packets, and execution packets. Full Hipson is optional and maintained at https://github.com/Hipson47/Hipson.git.

- Skill: `framecoreworks/hipson-adapter` (Agent Skill, multi-file: 5 files)
- Install (CLI): `npx skillmds@latest add framecoreworks/hipson-adapter`
- Raw SKILL.md: https://api.skillmd.com/api/skills/framecoreworks/hipson-adapter/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Research & Search
- Author: FrameCoreWorks (https://skillmd.com/u/framecoreworks)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/framecoreworks/hipson-adapter

---


# Hipson Adapter

This is the lightweight adapter, not the full Hipson system.

## Language Policy

Public instructions and installation guidance stay in English. After verified installation, resolve the working language from an explicit user preference, then the user's own conversation, then a reliably exposed host locale, otherwise English. Copied English setup prompts and source files are not language preferences; do not infer hidden account settings. Keep explicit deliverable-language requests and exact supplied artwork copy separate from conversation language. Do not translate or rewrite public source files to localize a session.

## When To Use

Use this skill when:

- A workflow role needs a bounded research map, internet mapping packet, review packet, or execution packet.
- The user wants Hipson-style instruction structure without connecting the full Hipson repository.
- A task benefits from clear target role, goal, exclusions, evidence rules, acceptance criteria, and output schema.

Do not use this skill as the workflow orchestrator, evidence verifier, or external research runner.

## Inputs

Required:

- `target_role`: role ID that should receive the packet.
- `goal`: concrete outcome the packet should enable.
- `context`: brief, references, source constraints, or repo evidence.
- `exclusions`: what the receiver must not do.

Optional:

- `source_rules`: allowed sources, evidence quality, or search boundaries.
- `acceptance_criteria`: how the packet will be judged.
- `output_schema`: required structure for the receiving role.

## Outputs

Produce one lightweight Hipson-style packet:

- Research Map
- Internet Mapping Packet
- Bounded Instruction Packet
- Review Packet
- Execution Packet

Full Hipson can be connected separately from:

https://github.com/Hipson47/Hipson.git

## Process

1. Confirm the target role and packet type.
2. Compress context into only what the receiver needs.
3. State exclusions, evidence rules, and acceptance criteria before the method.
4. Define the output schema so the receiver does not improvise shape.
5. Hand the packet back to `workflow-orchestrator` or the named target role.

## Decision Rules

- Use the lightweight adapter by default.
- Mention full Hipson only as an optional expansion path, not a required dependency.
- If the task requires full Hipson repository knowledge, state that the adapter can only prepare the connection request.
- Keep packets bounded; do not turn them into long research essays.

## Guardrails

- Do not replace workflow orchestration.
- Do not perform full research by default.
- Do not run external tools or claim external verification.
- Do not treat adapter output as verified truth.
- Do not include private workspace context, credentials, local paths, or non-public examples.

## Handoff

Review gate: `instruction_packet_fit`.

Hand off with:

- `packet_id`
- `target_role`
- `packet_type`
- `goal`
- `context`
- `exclusions`
- `source_rules`
- `acceptance_criteria`
- `output_schema`
- `handoff_target`

## QA Checklist

- Packet target and goal are explicit.
- Context is sufficient but not bloated.
- Exclusions and source rules are concrete.
- Output schema is usable by the receiver.
- Full Hipson is described as optional and separate.
- No external execution or verification is implied.