pull
Skill1 starsChanged 8 days agoMITView on GitHub
Pull your active Jira sprint into Claude Desktop. Use when the user asks to pull, sync or load their sprint. Makes this session the sprint's main session, creates one folder and one task session per unfinished task, and writes summary.md. Read-only on the tracker.
15 other projects use a version of this.
Adopted by
Most recently taken up by
- markmhendrickson/neotomatheir own version, first seen Nov 15, 2026
- toy-crane/claude-code-playbook-templatetheir own version, first seen Nov 8, 2026
- egregore-labs/egregoretheir own version, first seen Nov 6, 2026
- grainulation/grainulatortheir own version, first seen Nov 3, 2026
- iagocavalcante/claude-turbo-searchtheir own version, first seen Oct 27, 2026
- MarvinJWendt/skillstheir own version, first seen Oct 15, 2026
Used with
Projects with it also use ingest.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
JaimeGBASkillingest
Digest an external source (article, paper, transcript, URL, book chapter) and integrate its content into the knowledge base
Also in 3 projects that use this
Other versions15 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 15
- openai/symphony★ 27ksame name
- egregore-labs/egregore★ 293same name
- team-mirai-volunteer/mirai-gikai★ 214same name
- grainulation/grainulator★ 86same name
- HamedMP/matrix-os★ 86same name
- toy-crane/claude-code-playbook-template★ 77same name
- markmhendrickson/neotoma★ 38same name
- Itsokay-co/bio-vibing★ 17same name
- iagocavalcante/claude-turbo-search★ 16same name
- matcom/ai-skills★ 14same name
5 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 4 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 12 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Never write to the tracker.
- Very specific: line 13
Desktop: If no mcp__ccd_session__start_session tool exists (loaded or deferred), send error.desktop-only (in the user's language) and stop.
- Very specific: line 16
Profile: Read ~/.config/rabbit/profile.md (its Workflow: line is not used here).
- Distinctive: line 18
If it is missing or unreadable, or a required value is empty (Basics: Workspace, Repositories folder, Chat language, Document language.
- Very specific: line 39
Search with jql: "assignee = currentUser() AND sprint in openSprints() ORDER BY key", fields: ["summary", "status", "issuetype", …
- Very specific: line 69
If refused because this session is nested, run mcp__ccd_session_mgmt__detach_session with "self" and move again.
- Distinctive: line 103
Do not move task sessions: they nest under this session and follow it.
- Distinctive: line 105
Before the batch, write a bold title line and one sentence.
- Very specific: line 109
Write SPRINT_DIR/summary.md in DOC_LANG following references/summary-format.md.
“Common” is measured: kept by at least 6 in 10 of the 12 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Pull
Never write to the tracker. Run the steps in order; stop and ask when a step says so.
0. Before anything
- Desktop. If no
mcp__ccd_session__start_sessiontool exists (loaded or deferred), senderror.desktop-only(in the user's language) and stop. Create nothing. - Profile. Read
~/.config/rabbit/profile.md(itsWorkflow:line is not used here). If it is missing or unreadable, or a required value is empty (Basics: Workspace, Repositories folder, Chat language, Document language; Tracker: Site, Tools, Sprint field), sendsetup.needednaming what is missing, run therabbit:setupskill with the Skill tool, and when it finishes continue here. Site or Tools still empty after setup: stop (setup has said what to connect). Sprint field still empty (no sprints on this site): senderror.no-sprintand stop. - Language.
LANG= Chat language, or forautothe language of the user's last message (English if none).DOC_LANG= Document language, orLANGforauto. Every message stays inLANG, even after text in another language. Send fixed messages fromreferences/messages.mdby id, translated; keep Markdown,{{...}}values, paths, keys and commands as they are.
Constants: FIELD = Tracker Sprint field; tracker calls use the profile's Tools
(with cloudId = Site when the tool takes one); WORKSPACE = Basics Workspace
with ~ expanded; sidebar section Sprints.
1. Read the sprint
Search with jql: "assignee = currentUser() AND sprint in openSprints() ORDER BY
key", fields: ["summary", "status", "issuetype", "priority", "labels",
"parent", "description", FIELD], maxResults: 100. Never ask for an "evidence"
or expanded view. Follow the tool's paging (for example nextPageToken until
isLast, or startAt) until every issue is read.
From each issue's FIELD keep the active entries: state active in any case,
or a string entry such as …Sprint@x[id=12,…,state=ACTIVE,name=…] (Jira
Server/Data Center), read the same way. No issue: send error.no-sprint and
stop. If they span more than one sprint id, send ask.which-sprint with the
list, end the turn, and keep only the chosen sprint's issues.
SPRINT_ID = that sprint's id; LABEL = SP_<SPRINT_ID>;
SPRINT_DIR = "<WORKSPACE>/<LABEL>" (always quote paths).
Unfinished keys: the same JQL with AND statusCategory != Done before ORDER
BY (fields: ["summary"]), kept only when the key is among the chosen sprint's
issues. Do not infer status categories from status names.
2. Become the sprint's main session
mcp__ccd_sidebar__list_sections: take the first section namedSprints; none: create it withmcp__ccd_sidebar__create_section.mcp__ccd_session_mgmt__list_sessionswithlimit: 500(this session is never in the result).- A session titled exactly
LABELmeans another session is this sprint's main session: senderror.other-mainlinking it as[<title>](#<sessionId>)and stop. Create nothing. - Otherwise move this session into the section
(
mcp__ccd_sidebar__move_sessions,session_ids: ["self"],section_id). If refused because this session is nested, runmcp__ccd_session_mgmt__detach_sessionwith"self"and move again. Title itLABEL(mcp__ccd_session_mgmt__set_session_title,"self"). mkdir -pSPRINT_DIRandmcp__ccd_directory__change_directoryto it (it applies after this turn; until then use absolute paths).
3. Decide which tasks need a session
mcp__ccd_session_mgmt__get_session with "self" gives this session's id;
mcp__ccd_session_mgmt__list_sessions with linked: true, include_archived:
true, limit: 500 lists the sessions it started. A task already has a session
when one of them has startedBy equal to that id and a title matching
(^|[^A-Z0-9-])<KEY>([^0-9]|$). A task whose folder <WORKSPACE>/*/<KEY>/
exists outside SPRINT_DIR (an earlier sprint, or tasks/) is carried
over: its session
and documents stay there; create no folder or session for it. Missing =
unfinished, not carried over and no session. Finished tasks and tasks that left
the sprint are never touched.
4. Prepare folders
mkdir -p SPRINT_DIR/<KEY> for every unfinished task. Never delete or
overwrite anything in an existing task folder.
5. Open the missing task sessions
For each missing task, in key order:
- Title:
<KEY>+ the summary with leading[...]tags and spaces removed; over 60 characters: cut to 59 and append…. - Fill
references/task-session-prompt.mdand callmcp__ccd_session__start_sessionwithinitiation: "user_asked",context: "fresh",cwd: <task dir>,use_worktree: false,title,prompt= filled Prompt section,background= filled Background section. Do not passpermission_modeormodel. - Do not move task sessions: they nest under this session and follow it.
Before the batch, write a bold title line and one sentence.
6. Write summary.md
Write SPRINT_DIR/summary.md in DOC_LANG following
references/summary-format.md.
7. Report
Send report.done. If sessions were opened, send report.ready once when each
has finished its first turn, and stop.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

