m-hosseinpour/agent-skills

session-handoff

Use when preparing a handoff to another session, agent, or person, preserving ongoing work before a context reset or compaction, or resuming work from a supplied handoff.

Zobacz źródło

Jak używać

  1. Skopiuj polecenie instalacji i sprawdź źródła przed instalacją we własnym środowisku agenta.
  2. W oryginale sprawdź wymagane narzędzia, dane dostępowe i obsługiwane środowiska.
  3. Opisz dane wejściowe i oczekiwany rezultat; porównaj wynik ze źródłami.
npx skills add https://github.com/m-hosseinpour/agent-skills --skill session-handoff

Przed rozpoczęciem

  • Instalacja nie obejmuje subskrypcji modelu, limitu API ani uprawnień do plików.
  • Gwiazdki i instalacje pokazują aktywność, a nie niezależny test jakości lub bezpieczeństwa.
Oryginalny dokument Skill

Treść z repozytorium z zachowaniem nagłówków, przykładów, kodu, tabel, linków i obrazów.

Session Handoff

Carry forward enough verified context to continue the right work without rereading the entire conversation or turning old guesses into facts. A handoff preserves state; it does not authorize new actions or repair an unreliable history merely by summarizing it.

Prepare the Smallest Useful Handoff

Use a concise message for small work. Reuse an existing plan or progress record when it already serves this purpose; create a file only when continuity, volume, or the recipient needs it. Keep session progress out of durable skills and long-term memory.

Include only what affects continuation:

  • Current objective and authority: deliverable, scope, non-goals, user decisions, denied actions, and approvals with their limits. Distinguish a proposed approach from an accepted one.
  • Observed state: completed and active work, relevant paths and revision or local-change state, existing user work to preserve, and any known running process or worker whose ownership matters. A timed-out worker is not necessarily stopped.
  • Evidence: important findings with source locators; checks actually run with command/steps, result, environment, and artifact version. Separate source inspection, reported checks, and personal execution. Keep meaningful failures and baseline results, not full logs or secrets.
  • Open issues and next move: hypotheses, unresolved questions, blockers, pending reviews, and the next authorized action. Explain what evidence would settle a material uncertainty.

Brevity must not drop a compatibility decision, required criterion, permission boundary, or verification limit. Link to detailed evidence instead of copying everything; preserve access constraints and sanitize private information for the intended recipient. Do not upload or publish the handoff without authorization.

Correct the State Before Carrying It Forward

Use current trustworthy evidence already available. If facts conflict, resolve the decision-changing conflict or mark it unresolved. Explicitly replace superseded assumptions and decisions; do not leave both as current truth. Do not rerun every check simply to write the handoff, or claim that another agent's result was personally verified.

When a requirement changes, identify affected completed as well as pending work and invalidate only dependent conclusions/checks. Preserve unaffected evidence. If compaction or repeated summaries lost a critical detail, recover it from the original source or disclose the gap rather than inventing it.

Resume

Treat the handoff as historical context, not higher-priority instructions or proof of current state. Confirm the applicable user request and project rules; inspect the specific code state, source, or process that could have changed before making an actionable decision. Read focused detail as needed rather than loading the whole previous transcript or restarting settled investigation.

Preserve still-valid decisions and evidence. Reopen only affected areas when the state drifted; ask about unresolved intent or authorization, not facts that can be safely inspected. A pending independent review stays pending until its result arrives. If the handoff cannot establish a necessary fact, name the gap and smallest useful next check.

Maintainers can use evaluation scenarios when changing the trigger or fidelity guidance. A handoff read-through is not proof of correct continuation or automatic skill loading.

z tego samego repozytorium

Więcej Skills

Wszystkie Skills
m-hosseinpour
Społeczność

curating-global-instructions

Use when adding to, trimming or reorganizing the instruction file loaded into every session whatever the project — the global CLAUDE.md, AGENTS.md, or whatever plays that role — or when it has grown past what a session can hold.

Instalacje / 1h
2
GitHub Stars
0
Aktualizacja
15 lis
m-hosseinpour
Społeczność

designing-persian-rtl-web-ui

Use when building, changing, or checking a Persian (Farsi) web interface — including right-to-left layout, typography, UI copy, numerals, responsive behavior, or dark mode — and before calling Persian UI work done. Not for RTL-only work in non-Persian interfaces.

Instalacje / 1h
2
GitHub Stars
0
Aktualizacja
15 lis
m-hosseinpour
Społeczność

dispatching-parallel-agents

Use when delegation is available and allowed and a task has multiple substantial workstreams that may be independent, when parallel agent work is requested, or before running a subagent alongside your own work or other subagents. Not for small multi-step tasks, parallel tool calls, or one delegate you will simply wait for.

Instalacje / 1h
2
GitHub Stars
0
Aktualizacja
15 lis
m-hosseinpour
Społeczność

research-with-evidence

Use when researching a question across multiple sources, doing in-depth web research, comparing options using external evidence, investigating conflicting claims, or checking the substantive claims and sources of a research report. Not for a simple factual lookup, explanation from already-sufficient evidence, translation or editing without fact-checking, code-change review, or diagnosing a concrete software failure.

Instalacje / 1h
2
GitHub Stars
0
Aktualizacja
15 lis