Przejdź do treści
Biblioteka skilli
Produktywność osobista · Automatyzacja

afk

/afk

Pozwala kontynuować pracę samodzielnie podczas dłuższej nieobecności użytkownika, także jako siesta, bez czekania na odpowiedzi.

Licencja
CC-BY-4.0
Ostatnia zmiana repozytorium
05.11.2026

Ocena i bezpieczeństwo

90/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść25 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
2
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
1
Przestarzałość

Brak sygnałów. Repozytorium zmienione 05.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

CC-BY-4.0, otwarta.

Co robi i kiedy

Pozwala kontynuować pracę samodzielnie podczas dłuższej nieobecności użytkownika, także jako siesta, bez czekania na odpowiedzi.

Oryginalny opis (EN)

Continue the session fully autonomously because the user is leaving for an extended period (also invoked as /siesta). Use when the user invokes /afk or /siesta, or explicitly says to keep working unattended while they are away. Not for ordinary turns where the user is still around to answer questions, nor for moving the session to the cloud first (afk-teleport), nor for a disposable build to try and maybe discard (prototype).

Jak działa

  1. Carry the work forward
  2. Ledger
  3. When you may stop
  4. Final report
  5. Closing
Sekcje z nagłówków SKILL.md, w oryginale · 51 linii, 694 słów
Podgląd SKILL.md
---
name: afk
description: >-
  Continue the session fully autonomously because the user is leaving for an extended period
  (also invoked as /siesta). Use when the user invokes /afk or /siesta, or explicitly says to
  keep working unattended while they are away. Not for ordinary turns where the user is still
  around to answer questions, nor for moving the session to the cloud first (afk-teleport),
  nor for a disposable build to try and maybe discard (prototype).
license: CC-BY-4.0
metadata:
  author: Alexandros Andre Chaaraoui
  source: https://github.com/alexandrosandre/agentic-engineering
---

# afk

The user is away and cannot answer questions until they return. Work like a principal engineer left in charge: keep the task moving, ground choices in evidence, and don't get stuck on nits or analysis-paralysis. Stopping to ask is almost always wrong — stop early only on hard blockers: destructive or irreversible actions, rules that require explicit permission, or access only the user can grant.

Standing rails, whatever stage the session is in:

- All AGENTS.md rules stay in force — autonomy widens which decisions you take, not what you are allowed to touch.
- Merge authority stays with the user: never merge, and never invoke the merging skills (/lgtm, /yolo).
- Involving other people stays with the user: never @mention, CC, FYI, assign, or request review from anyone, anywhere (PR bodies, comments, issues, automation prompts), and never suggest whom to involve — a mention notifies a real person, in the user's name, about work the user has not approved yet. Leave addressee slots blank; the user routes attention when they return.
- Don't hand work back: no task chips for the user to click later — that is the work this run exists to do. Do it, or ledger why not.

## Carry the work forward

Pick up the session wherever it is and take each stage into the next:

- **Designing** — review the design doc (/design-review), then plan the implementation, then implement.
- **Planning** — review your plan critically, then implement it.
- **Coding** — finish the implementation, then take it through the delivery pipeline via a non-merging shortcut (/ship-it, or /ship-it-lite for low-risk changes). Invoke the shortcut rather than hand-rolling its steps: /create-pr on its own skips the review pass, the half the user cannot start while away. Work landing later needs it run again.

A pipeline step that pauses for user confirmation or finding triage (e.g. /contextual-review) must not stall the session: disposition what is clear and consequential yourself, and carry the rest into the final report.

## Ledger

Keep a ledger from the start of the run, outside the worktree — the session scratchpad is fine — where the pipeline cannot sweep it into a commit. Head it with the run's remaining steps and keep them current: after a compaction, that file is what says where the run had got to.

At any fork where you would normally ask the user which path to take:

1. Record the decision point in the ledger.
2. Analyze each option's pros and cons. Where an experiment can settle it, run one — local benchmarks or prototypes only, never with production data or side effects.
3. Take the winner and keep moving. When evidence is thin, prefer the reversible option.

Ledgered decisions are provisional calls made in the user's absence; the final report is where the user ratifies them. Never record one in a design doc as if the user had made it — flag it in the report instead (see AGENTS.md on design docs).

## When you may stop

When every item you know of is done, ledgered, or genuinely blocked on the user. A "what remains" list in your report is usually work this run should have taken — re-read it and pick the next item first. A prompt arriving mid-run is added scope, not a handoff back.

## Final report

When you stop — done or blocked — report:

- How far you got and what remains, including the PR if one was opened.
- The ledger: one short paragraph per decision, written to be ratified cold — what the product or the user now gets versus before, the options considered, and the evidence behind the winner, in the product's vocabulary (a customer account, a report, a permission), never a label list or harness shorthand (criteria, goldens, findings).
- Anything still blocked on the user, as questions answerable from the report alone — never from the run's transcript.

## Closing

- End your response with a blockquote line: **Skills used:** then each skill name in backticks (this skill: `afk`; include other skills if used).
- If this skill's instructions failed or needed a workaround, update this file.
Pliki w paczce (2)
  • README.md 2 KB
  • SKILL.md 5 KB

Wersje

RepozytoriumWynikLicencja
Ta strona · alexandrosandre/agentic-engineering90CC-BY-4.0
finolabs/finolabs-vibecode100MIT
fabricio21x/fbs100MIT
alexandrosandre/alice-issue-agent90CC-BY-4.0

Migawka bazy z 13.11.2026 · wersja paczki 35d61b68d638 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 90afk-teleport
    Przenosi sesję do agenta w chmurze i dalej pracuje samodzielnie, gdy użytkownik wychodzi, a komputer może przejść w uśpienie.
  • 90dev10x:afk
    Ustawia tryb pracy bez nadzoru dla długich sesji, żeby zadanie nie stawało na bramkach potwierdzeń.
  • 100prototype
    Buduje jednorazowy prototyp do wypróbowania: po jednej rundzie pytań działa autonomicznie, z dziennikiem decyzji i szkicem PR.
  • 90dft-siesta
    Kieruje zapytania o SIESTA do właściwych podskilli wedle intencji: obliczenia statyczne, relaksacja, dynamika molekularna lub przygotowanie analizy elektronowej, z jednolitym przekazaniem do skilli zleceń.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.