Przejdź do treści
Biblioteka skilli
Zarządzanie i produkt · Automatyzacja

get-connected

/get-connected

Na kroku zerowym procesu odkrywania produktu sprawdza dostęp do repozytorium i trackera oraz zapisuje ustawienia połączenia.

Repozytorium
paqad-ai ↗
Licencja
MIT
Ostatnia zmiana repozytorium
12.11.2026

Ocena i bezpieczeństwo

100/ 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ść35 / 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
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 12.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 robi i kiedy

Na kroku zerowym procesu odkrywania produktu sprawdza dostęp do repozytorium i trackera oraz zapisuje ustawienia połączenia.

Oryginalny opis (EN)

Chat and Claude Code: Step 0 of the product-discovery journey: confirms the repository and issue tracker are reachable, finds the evidence level and saves the connection setup. Use when the journey directs it to step 0, not directly.

Jak działa

  1. When this runs
  2. What it does
  3. If the checks cannot run
  4. Output
Sekcje z nagłówków SKILL.md, w oryginale · 115 linii, 1 230 słów
Podgląd SKILL.md
---
name: get-connected
description: "Chat and Claude Code: Step 0 of the product-discovery journey: confirms the repository and issue tracker are reachable, finds the evidence level and saves the connection setup. Use when the journey directs it to step 0, not directly."
compatibility: "claude.ai chat, Cowork or Claude Code; reads project docs and code through a connector, uploaded files or the open folder"
---

# get-connected

How to talk: follow `references/voice.md`. Short, answer first, plain business words, no narration,
one short sources line. Those rules win.

Step 0: get connected. Fills the `setup` block.

## When this runs

Directed by the product-discovery journey; not started directly.

## What it does

Work out which sources can be read, the repository first and the tracker second, and record them in
order in `setup.grounding_sources` (`references/ground-from-tracker.md`).

1. Choose and reach the repository by capability (`references/connect-repository.md`), then detect
   its evidence level (`references/evidence-levels.md`) with `scripts/check_onboarded.py`. project-docs (ready): carry on from project docs.
   docs-and-code (partly ready): carry on, say its message once and name the areas without a summary
   as not documented. code-only (not set up, with reachable code): carry on from code by names, as
   what the code suggests. Stop only when nothing is readable. Store the choice in `setup.repository`, its state in `setup.repository_state`,
   and the level in `setup.evidence_level`. When a repository connector is switched on but offers no
   list or read action, say this once and carry on tracker only, with `setup.repository_state`
   `connector-unreadable`:
   "GitHub is connected, but I can't read any repositories through it from here. I'll work from the tickets for now. To use the code and docs, attach the repository or its docs folder."
   A read that fails on sign-in or a rate limit is not this case and never gets that sentence. With
   no readable tracker either, say nothing can be read, as in step 3, and stop.
2. Find the Jira project from the repository, before any tracker read. With no readable repository
   skip this and ask which project to use. With the repository connector's list actions, resolved by
   capability, read up to 100 branch names and the subjects of the last 50 commits on the default
   branch, newest first, and pipe them one per line to `scripts/find_ticket_keys.py`. Store only its
   counts in `setup.ticket_key_scan`: `lines_read`, each prefix with its count, and `github_refs`.
   Drop each prefix's `examples` list before recording; never store examples, branch names or
   commit text, or the record check refuses the scan. Then, by the top prefix's hits:
   - One clear prefix (at least 3 hits and at least twice the next): set `setup.tracker_kind` to
     `jira`, check that project with one read, then recommend it in one choice prompt, with a
     different project as the other option, saying, with ABC the prefix found:
     "Your branches and commits mostly mention ABC tickets, so I'll use the ABC project in Jira."
     If that one read fails (not found, renamed or not visible), say once why and ask instead.
   - Several close prefixes (at least 3 hits, less than twice the next): one choice prompt, most
     hits first, the top one recommended, plus a different project.
   - Fewer than 3 hits: recommend nothing; ask which Jira project to use, with the prefixes found
     as plain choices plus a different project.
   - Only GitHub refs such as `#123`: set `setup.tracker_kind` to `github` and follow
     `references/tracker-profiles-github.md`.
   - Nothing found, nothing read or no list actions: ask which Jira project to use.
   A list that errors or is cut short still counts: scan the lines read and record `lines_read`;
   ask only when nothing was read. A failed list read never makes the repository unreadable.
   When the keys point clearly to a Jira project but only GitHub is connected, name that Jira
   project once and let the person choose: connect Jira now, or carry on with GitHub and export
   the tickets. Record `setup.project_key_source` as `repository` when the person takes the
   recommended project, and `asked` otherwise. Never search the tracker broadly to pick a project.
3. With no readable repository, skip `scripts/check_onboarded.py` and check the tracker next. If the
   tracker is readable, set `setup.evidence_level` to `tracker-only` and say once:
   "No repository is connected, so I'll work from the tickets in your tracker. Tickets show what was planned or asked for, not what is built."
   If neither is readable, say this, invent nothing and stop:
   "I can't read a repository or the tracker from here, so there is nothing to ground this on. Attach the repository or its docs folder, or switch on the tracker connector, and I'll carry on."
4. Check the tracker for reading and for writing separately (`references/connect-tracker.md`).
   Readable: one read-only search in the target project answers. Store `setup.tracker_readable`.
   Writable: the connector offers a create action for the target project and the user can create
   issues there (PUB-7). Store the project's issue types, required fields, link types and the size
   and sprint field ids (PUB-1) in `setup`.
5. If the tracker is readable but not writable, do not stop: say once, before grounding starts,
   that the tickets will leave by export, and carry on. If it is neither, stop before drafting. Say
   plainly what is missing (connector off, no write tools, or no create permission) and who
   usually fixes it, and offer the export fallback (PUB-7, PUB-8).
6. Warn once, here, that every created issue carries a run label and run labels accumulate in the
   site's label list (PUB-4).

Action names differ by connector version: resolve each from what the connector exposes, never a
hard-coded tool name. Jira specifics: `references/tracker-profiles-jira.md`.

GitHub follows `references/tracker-profiles-github.md`: GitHub Issues is export only (host GitHub
connectors are read only). Record the kind as GitHub, export only, and route the hand off to the
export fallback (PUB-7, PUB-8) without checking for a create action.

## If the checks cannot run

Do the onboarded check by hand:

- List the `docs/modules` folders and read each one's `index/summary.md`. Treat an empty or
  whitespace-only summary as missing.
- Look for `docs/instructions/registries/modules.md`, the modules list; empty counts as missing.
- project-docs (ready): the modules list plus at least one summary. docs-and-code (partly ready): a
  summary but no modules list; carry on as above and say the exact sentence in
  `references/connect-repository.md` once. code-only (not set up): no summary; carry on from code by
  names as what the code suggests, never stopping a readable-code repository. Record the level in
  `setup.evidence_level`.

With no readable repository, skip the onboarded check: follow `references/ground-from-tracker.md`
for the tracker-only sentence, or the stop sentence when the tracker cannot be read either.

Pick the Jira project by hand as in `references/connect-tracker.md`: count the ticket key prefixes
in the branch names and commit subjects you can see, with the same thresholds, and ask when none
reaches 3 hits. Record only the counts in `setup.ticket_key_scan`, never the example keys.

Then do the tracker checks by hand (PUB-1 and PUB-7):

- Try one read-only search in the target project and record whether it answered.
- Confirm a create-issue action exists for the target project and the user can create issues there;
  if not, offer the export fallback, and stop only when the tracker cannot be read either.
- Record the issue types, required fields, link types, and the size and sprint custom field ids
  (from the issue type's full field list) in `setup`.

## Output

The `setup` block: the readable sources in order (`setup.grounding_sources`), the chosen repository
(`setup.repository`), its state (`setup.repository_state`, ready or partly-ready) and its evidence
level (`setup.evidence_level`, project-docs, docs-and-code or code-only, or tracker-only with no
repository), whether the tracker can be read (`setup.tracker_readable`), tracker kind, project key, epic and story types,
issue types, required fields, link types, size and sprint field ids, whether the user can create
issues, the run label (the run id in lowercase), where the project key came from
(`setup.project_key_source`) and the ticket key counts (`setup.ticket_key_scan`).
Pliki w paczce (2)
  • SKILL.md 8 KB
  • references/connect-tracker.md 4 KB

Wersje

RepozytoriumWynikLicencja
Ta strona · eliyce/paqad-ai100MIT
eliyce/paqad-ai100MIT

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

  • 90shape-idea
    Odtwarza pomysł na trzecim kroku ścieżki odkrywania produktu, pokazuje opcje, kompromisy i zalecenie.
  • 90understand-idea
    Doprecyzowuje cel, odbiorców, sukces i ograniczenia pomysłu na produkt jako pierwszy krok procesu odkrywania.
  • 100om-setup-discovery-pipeline
    Konfiguruje w repozytorium bramki odkrywania produktu obok potoku dostawy: role, ustawienia, zasady gotowości i katalog badań.
  • 100setup-issue-tracker
    Wybiera lub zmienia miejsce, w którym żyją zgłoszenia i intencje funkcji, i uzupełnia docs/agents/issue-tracker.md.
  • 80Keeping the tracker in step with Work
    Pilnuje, by status zgłoszenia w trackerze zgadzał się z postępem pracy, także wydania i linki do pull requestów.
  • 90sy-tracker-plan
    Planuje wycinki gotowe do trackera z zależnościami, etykietami, polami akceptacji i miejscami na walidację, w strukturze zgodnej z Linear, bez zmieniania samego trackera.

Uwagi i zgłoszenia

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