Turn a short, redacted Session summary into a collaboration-safe Context excerpt. Use before sharing an agent or meeting handoff when the original Session may contain private details that do not belong in the next task.
编程
klik-context-receipt
试用Turn a short, redacted work update into a reviewable Context Receipt that records source, freshness, scope, authority, open questions, and a human-return condition. Use when an agent or person needs to hand off or resume work without treating stale Context as current authority.
它能做什么
Turn a short, redacted work update into a reviewable Context Receipt that records source, freshness, scope, authority, open questions, and a human-return condition. Use when an agent or person needs to hand off or resume work without treating stale Context as current authority.
技能文档
Klik Context Receipt
Use this as a non-executing documentation workflow. It creates a concise, human-reviewable receipt; it does not access accounts, send messages, operate tools, make commitments, or authorize action.
Ask For Only What Is Needed
Request a short, redacted description of:
- Source — The Session, note, or artifact that supports the work.
- Freshness — When the source was last checked and what could invalidate it.
- Scope — What the next person or agent may prepare, and what is outside scope.
- Authority — Existing approval, an expiry if known, and whether new access is needed.
- Open questions — The one or two facts that must be clarified before preparation continues.
Do not request credentials, full recordings, private transcripts, client data, financial information, health information, or other sensitive material. A short redacted summary is enough.
Create The Receipt
Return this exact structure:
## Context Receipt
**Source:** [redacted artifact or Session]
**Freshness:** [last checked time] · **Invalidators:** [what would make it stale]
**Current Context:** [two or three factual bullets]
**Allowed preparation:** [bounded draft or analysis only]
**Not authorized:** [access, judgment, commitment, or tool action not already approved]
**Open question:** [the most important missing fact]
**Return to a person when:** [new access, judgment, external commitment, or conflicting Context]
Guardrails
- Treat the receipt as a review aid, not a permission grant.
- If the source is missing, stale, contradictory, or ambiguous, write that explicitly and return the decision to a person.
- “Allowed preparation” means a draft or plan for review. It never authorizes execution.
- Do not infer support for a recorder, model, provider, tool, integration, or product feature from the receipt.
Related Klik Link
相关技能
Turn a proposed AI follow-through step into a compact Action Readiness Card that makes source, freshness, scope, authority, expected result, and human-return conditions explicit. Use before preparing a consequential next step from remembered Context.
Review a proposed AI next step and classify it as ready to prepare, clarify first, or return to a person. Use when a user asks whether an AI workflow should continue, needs more Context, or requires human review before a consequential action.
Import your agent's memory files and scheduled tasks into Klik. Discovers memory files and scheduled tasks from the current agent's storage, lets you review and clean them, then uploads securely to Klik. Requires a 6-digit import code from Klik App > Settings > "Import from Agent". Triggers: "import to klik", "migrate memory to klik", "upload my memory to klik", "send my scheduled tasks to klik", "klik import".
Use this skill when reorganizing data/ and context_hooks in a briefing_package to avoid token waste. Triggers on: data vs context hooks, reorganize data file...
Review what an LLM feature or agent actually puts in its context window — and find what's bloating, missing, or fighting itself. Use when asked to review a s...