confluence-workflow
Skill1 starsChanged 3 months agoMITView on GitHub
Fetch and search Telekom Confluence wiki pages. Use whenever a wiki.telekom.de link or pageId appears, or when asked to look up, read, or search Confluence/wiki content. Covers fetching by pageId, search-then-fetch, and the confirm-before-write rule.
In this repository45 other files it gives its agents.
- AGENTS.mdAGENTS.md
- blast-radiusSkill
- broSkill
- codebase-designSkill
- code-reviewSkill
- creating-a-pr-mrSkill
- defuddleSkill
- diagram-designSkill
- docxSkill
- domain-modelingSkill
- engineering-principlesSkill
- forgejo-cliSkill
- frontend-designSkill
- gh-cliSkill
- git-conventional-commitsSkill
- git-working-agreementSkill
- glab-cliSkill
- grillingSkill
- grill-meSkill
- grill-with-docsSkill
- howSkill
- improve-codebase-architectureSkill
- jira-workflowSkill
- json-canvasSkill
- k8s-opsSkill
- obsidian-basesSkill
- obsidian-cliSkill
- obsidian-markdownSkill
- openspec-workflowSkill
- pdfSkill
- pptxSkill
- prototypeSkill
- researchSkill
- setup-matt-pocock-skillsSkill
- skill-minerSkill
- technical-writingSkill
- theme-factorySkill
- to-specSkill
- to-ticketsSkill
- triageSkill
- unslopSkill
- wayfinderSkill
- whySkill
- writing-for-agentsSkill
- xlsxSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
Use confluence_search first to locate candidate pages.
- Distinctive: line 22
Don't rely on the search snippet alone — fetch the full page before reasoning about its content.
- Distinctive: line 30
Always confirm immediately before destructive, irreversible, privilege-changing, or materially broader work, including deletion, moving …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Confluence workflow
Trigger: links like https://wiki.telekom.de/pages/viewpage.action?pageId=3691938421,
or any request to read/search the wiki.
Fetching a known page
- Extract the
pageIdfrom the URL and fetch with the telecontextconfluence_get_pagetool.
Finding a page
- Use
confluence_searchfirst to locate candidate pages. - Then fetch the full content of the best match with
confluence_get_pageusing itspageId.
Don't rely on the search snippet alone — fetch the full page before reasoning about its content.
Writing / mutating
- An explicit user request that names the Confluence target and a bounded write action authorizes that action.
- Otherwise, present the exact change and ask for confirmation before writing.
- Always confirm immediately before destructive, irreversible, privilege-changing, or materially broader work, including deletion, moving page trees, access changes, and bulk edits.
- Recheck the space, page id, and mutation before applying it.
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.

