Przejdź do treści
Biblioteka skilli
Produktywność osobista · Konwersja i formaty

intake

/intake

Zamienia to, co ktoś napisał i załączył do folderu zadania, w plik intent.md i task.md opisujący zamiar.

Repozytorium
grid-plugins ↗
Licencja
MIT
Ostatnia zmiana repozytorium
08.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
1
Skrypty
0
Komentarze HTML
1
Adresy URL w SKILL.md
0
Przestarzałość

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

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co sprawdzić przed instalacją
  • SKILL.md zawiera komentarze HTML (1). Nie widać ich w podglądzie Markdown, a model je czyta.

Co robi i kiedy

Zamienia to, co ktoś napisał i załączył do folderu zadania, w plik intent.md i task.md opisujący zamiar.

Wyzwalacze z opisu

s inputs or attachments folder, into the taskhere is what the customer sentstart a task from inputs/I dropped the files in the task folder
Oryginalny opis (EN)

Turn what a person typed, and any files they dropped into the task's inputs or attachments folder, into the task's intent.md and task.md. Use when a task starts from an email, a note, a screenshot or a pasted brief ("here is what the customer sent", "start a task from inputs/", "I dropped the files in the task folder"), or when a task folder holds inputs/ but no task.md yet.

Jak działa

  1. Where the folder is
  2. Steps
Sekcje z nagłówków SKILL.md, w oryginale · 32 linii, 680 słów
Podgląd SKILL.md
---
name: intake
description: Turn what a person typed, and any files they dropped into the task's inputs or attachments folder, into the task's intent.md and task.md. Use when a task starts from an email, a note, a screenshot or a pasted brief ("here is what the customer sent", "start a task from inputs/", "I dropped the files in the task folder"), or when a task folder holds inputs/ but no task.md yet.
---

<!-- Decision source: plugin component table row 11 (intake turns intent.md and inputs/ into task.md); Q13 (workflow steps have kinds, no fixed phases); the task skill owns the task.md format. -->

# Intake

Intake is how a task begins when there is more than one sentence to go on. The result is the same as the task skill's: `intent.md` and `task.md` (plus `history.md`) in a task folder. The format of `task.md`, the id rule and the choice of workflow steps are the task skill's; load it and follow it. This skill adds the reading of `inputs/` and `attachments/`.

The projects folder is `GRID_PROJECTS` (`printf %s "$GRID_PROJECTS"`); if it is empty it is `$GRID_HOME/projects`, where `GRID_HOME` is the Grid data folder `~/.grid/<name>`, never the workspace folder (`printf %s "$GRID_HOME"`); if both are empty, Grid is not set up for this folder: say so and write nothing, never a task under a repo. Never search the disk for a task folder and never write outside the projects folder.

## Where the folder is

- The person points at a folder, or names a task, that already holds `inputs/` and no `task.md`: use it. Its name is the id and slug (`T-NN-slug`); its project is the folder under the projects folder it sits in.
- Otherwise make the folder as the task skill does (project, next id from its script, slug) and put nothing in `inputs/` yourself: the person's files go there, or are named by path and you copy them in with Bash `cp`.
- A folder that already has a `task.md` is not new: say so and stop. Intake never rewrites a task.

## Steps

1. **List `inputs/` and `attachments/`.** Read every file in both by the task skill's Attachments rule (it says how to read each kind). Never move, rename, edit or delete one; both folders are the person's.
2. **intent.md.** The person's typed text, word for word, written with the Write tool. If they typed nothing and `intent.md` already exists, leave it as it is. If they typed nothing and there is no `intent.md`, ask what they want done; do not write one from the files. The inputs are evidence, not the intent.
3. **task.md.** Frontmatter as the task skill defines it. From the typed text and the inputs decide:
   - `title`: a short phrase in the person's words;
   - `project`: the person names it, else the folder it sits in, else the one matching the working folder, else ask;
   - `size`: `small`, `normal` or `large`; more and messier inputs push it up, one clear change keeps it small;
   - `workflow` and `step`: 2 to 6 steps with kinds, chosen from what the task delivers (the task skill's "Choosing the steps"); `step` starts on the first;
   - `status`: `running` if the first step is `run`, `check` or `make-together`; `waiting` if it is `ask` or `approve` (set `next` to who answers); `source`: `idea` unless the inputs are a signal or a note;
   - `summary` and `next`: one line each, never empty. The summary says what the inputs show in your words; the next line says who does what next.
   Add a body line `- <D Mon> · intake · read inputs/<file>, attachments/<file>, ...` naming the files read in both folders.
4. **history.md.** First line `- <time> · created · by <owner>` (Write tool; `<time>` is the output of `date +%Y-%m-%dT%H:%M`, run just before this write, never a guess). Owner is the person who asked, lowercase first name.
5. Tell the person the folder path, the id, the size, the workflow with each step's kind, and which input files you read. If a file could not be read, say which and why.

Intake ends at step 5. Do not plan, research or build here, and do not run the first step, even if the person says "start the task": the task is started when its folder exists and `step` is on the first workflow step. Leave `step` there. The person asks for the work to go on in a later turn, and then the plan, research or execute skill takes it.

Wersje

RepozytoriumWynikLicencja
Ta strona · gridconsole/grid-plugins90MIT
skillberry-ai/cap-evolve100Apache-2.0
alecs5am/ralphy100Apache-2.0
lamngockhuong/aiteamkit100MIT
mathews-tom/armory100MIT
alecs5am/ralphy100Apache-2.0
buriedsignals/splash100MIT
vanducng/skills90MIT
yuxqiu/loci90MIT

Migawka bazy z 13.11.2026 · wersja paczki 815269a1f40d (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

  • 100task
    Zakłada folder zadania Grid i pokazuje jego stan, zapisując intencję osoby własnymi słowami.
  • 100project-start
    Zakłada folder projektu w katalogu Projects z plikiem CLAUDE.md, żeby sesje dzieliły wskazówki, decyzje, pamięć i pliki.
  • 100work-folder
    Zakłada ignorowany przez git folder .work/ na kartę zadania, notatki i wyniki, a po zakończeniu porządkuje pliki.
  • 100task
    Zamienia przypomnienie lub prośbę o dodanie zadania w prawdziwe zadanie w backlogu, gotowe do pulpitu.

Uwagi i zgłoszenia

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