twg-agentic-search
Use with root twg for deep iterative enterprise/company knowledge search and internal research with Rovo Search across connected apps/connectors including Confluence, Jira, Drive, Slack, Bitbucket, and GitHub.
- Installs
- 92
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/atlassian/twg-cli --skill twg-agentic-search- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads twg-agentic-search automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
twg-agentic-search
Use together with the root twg skill. Exact command grammar comes from live
twg help, especially twg help describe "rovo search" when filter or output
options matter.
CLI launcher fallback
Run twg <command>. On shell command not found, use $HOME/.local/bin/twg
(macOS/Linux) / $env:LOCALAPPDATA\Programs\twg\bin\twg.exe (PowerShell), then
tell user to add that directory to PATH. Do not treat auth or command errors as
PATH failures.
Workflow
- Classify the request as fuzzy or cross-product internal research. Prefer this skill when the source is unclear, current company knowledge is needed, or the answer may span Confluence, Jira, Drive, Slack, Bitbucket, GitHub, or other Rovo-connected apps.
- Confirm or infer the Atlassian site. Ask only when no configured or explicit site is available and the ambiguity would change the search.
- If app/source availability changes the plan, run
twg rovo list-apps -o json. Use the returned built-ins, connectors, readiness, and auth/setup actions to decide scope; do not start setup or login unless the user asked for it. - Start with one query that combines the concrete topic with the requested artifact or decision type. Use at most one canonical/authoritative or recent/update-oriented refinement when the first result set mixes scopes, lacks primary sources, or misses the requested time signal. Do not fan out exact-title searches for every candidate already returned by the primary query.
- Choose filters deliberately. Default to Confluence and Jira built-ins for official/internal knowledge. Broaden to Slack, Google Drive, Bitbucket, GitHub, or other connectors only when useful and available. Use app, type, recency, owner/contributor/assignee/reporter/status, title-only, label/space, and site filters when they narrow evidence without hiding likely answers.
- Search with bounded output:
twg rovo search "<query>" --output json --output-summary auto --agent-fields @compact
twg rovo search "<query>" --output json --output-summary auto --agent-fields @evidence
Use @compact to shortlist candidates and @evidence when snippets, URLs, and
provenance need more detail.
Evidence Rules
- Treat search snippets as candidates, not facts.
- Hydrate a small, diverse primary-source set before final claims. For document
discovery, cover distinct roles such as requirements, architecture/design,
and current delivery rather than redundant pages. Use product-native
commands such as
twg confluence content get,twg jira workitem get,twg jira workitem query,twg bb pull-requests get <id>,twg bb repo get, or the relevant product command for the result URL/type. - For document or PRD discovery, select at most five sources across those roles. Hydrate one source per role unless a material conflict requires a second. Stop once the roles, current delivery, and important conflicts are supported, even when search returns more candidates.
- Prefer official spaces, owned project pages, current Jira issues, and recent decision records over personal drafts or stale chat mentions, unless the user explicitly asked for informal signal.
- Compare hydrated evidence for conflicts, recency, ownership, and authority.
- Do not rerun an
@evidencesearch for a candidate that can be hydrated through its product-native URL or ID, and do not refetch one source under another projection. Call out ACL gaps, unavailable connectors, low recall, and unresolved contradictions instead of flattening them into a single claim.
Output
Lead with the answer or best-supported conclusion. Cite hydrated titles/URLs and include the source app, date or status when available, and why each source was trusted. Separate confirmed facts, likely interpretations, conflicts, and gaps.
FAQ
What does the twg-agentic-search skill do?
Use with root twg for deep iterative enterprise/company knowledge search and internal research with Rovo Search across connected apps/connectors including Confluence, Jira, Drive, Slack, Bitbucket, and GitHub.
How do I install twg-agentic-search?
Run npx skills add https://github.com/atlassian/twg-cli --skill twg-agentic-search in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/twg-agentic-search/ (personal) or .claude/skills/twg-agentic-search/ (project).
Which AI agents can use twg-agentic-search?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is twg-agentic-search safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains twg-agentic-search?
It is published by atlassian in atlassian/twg-cli. It has 92 recorded installs.
More from atlassian/twg-cli
twg
atlassian/twg-cli
Use TWG whenever Atlassian or company context would help: Jira workitems and issues; Confluence pages and PRDs; Bitbucket PRs; project or goal status and launch readiness; owners, SMEs, approvers, or escalation; personal, org, or leadership work rollups and out-of-office catch-ups; dependency maps; code search, repository, or PR discovery; incidents, on-call, or reliability; and deep internal research across connected sources, docs, work, and people.
twg-confluence
atlassian/twg-cli
Use with root twg for Confluence content, spaces, hierarchy, authoring, editing, comments, versions, permissions, exports, and CQL. Applies Confluence semantics and safe write rules.
twg-jira
atlassian/twg-cli
Use with root twg for Jira workitems, similar issue discovery, duplicate detection, projects, boards, sprints, fields, transitions, comments, links, and administration. Applies Jira semantics and safe mutation rules.
twg-status-rollups
atlassian/twg-cli
Use with root twg for status rollups, personal work summaries, and decision-readiness or go/no-go briefs. Routes to pr-tree, org-tree, work-tree, or workitem-tree.
twg-engineering-work
atlassian/twg-cli
Use with root twg for code search, repositories using an API/package, implementation and reverse-dependency discovery, PR status and reviews, repo contributors, hot areas, and issue-to-PR lookups.
twg-context-discovery
atlassian/twg-cli
Use with root twg for deep context, dependency maps, related entities, project-to-repo discovery, OOO catch-ups, and "catch me up" requests around a concrete anchor.
Popular ai & agents skills
google-agents-cli-publish
google/agents-cli
This skill should be used when the user wants to "publish an agent", "publish my ADK agent", "register an agent with Gemini", "publish to Gemini" (formerly Gemini Enterprise), or needs guidance on the agents-cli publish gemini command. Also use when the user wants to "manage agents in Agent Registry", "list/update/delete registered agents", or "register an MCP server". Covers ADK vs A2A registration modes, programmatic and interactive usage, flag reference, auto-detection from deployment metadata, Agent Registry fleet management, and troubleshooting. Part of the agents-cli skills suite. Do NOT use for deployment (use google-agents-cli-deploy).
google-agents-cli-eval
google/agents-cli
This skill should be used when the user wants to "run an evaluation", "evaluate my agent", "evaluate my ADK agent", "write an eval dataset", "analyze eval failures", "compare eval results", "optimize agent", or needs guidance on the Gemini platform eval methodology and the Quality Flywheel. Covers eval metrics, dataset schema, LLM-as-judge scoring, and common failure causes. Applies to any agents-cli project, whatever framework the agent is written in. Do NOT use for agent API code patterns (ADK: use google-agents-cli-adk-code), deployment (use google-agents-cli-deploy), or project scaffolding (use google-agents-cli-scaffold).
skill-creator
anthropics/skills
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
codex-pet
prime-skills/runcomfy-agent-skills
Codex Pet generator on RunComfy. Build a Codex-compatible Codex Pet spritesheet.webp + pet.json from a single reference image, drop it into ${CODEXHOME:-$HOME/.codex}/pets/ / and Codex picks it up as a custom Codex Pet next to the 8 built-ins. This skill produces the exact Codex Pet atlas Codex expects (1536x1872 PNG/WebP, 8 cols x 9 rows, 192x208 cells, 9 animation states — idle, running-right, running-left, waving, jumping, failed, waiting, running, review). Calls OpenAI GPT Image 2 edit ONCE via the local RunComfy CLI as runcomfy run openai/gpt-image-2/edit to produce a canonical Codex Pet pose, then assembles all 9 animation rows programmatically with ImageMagick micro-transforms — no Codex Pro, no $imagegen, no OPENAIAPIKEY required, only RUNCOMFYTOKEN. Triggers on "codex pet", "create codex pet", "make codex pet", "hatch codex pet", "/hatch image", "desktop pet codex", "codex pets", "spritesheet.webp", or any explicit ask to build a custom pet for OpenAI Codex.
full-output-enforcement
leonxlnx/taste-skill
Overrides default LLM truncation behavior. Enforces complete code generation, bans placeholder patterns, and handles token-limit splits cleanly. Apply to any task requiring exhaustive, unabridged output.
executing-plans
obra/superpowers
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available