Pester Failure Analysis
PowerShell/PowerShell
Investigates failing Pester tests in PowerShell CI jobs by following a six-step workflow from pull request status to documented fix recommendations.
A skill your agent uses when the team context did not appear at session start, a skill failed to trigger, the install behaves unexpectedly, or someone asks why a session ran without team rules —…
Install Team Diagnose
$ npx skills add tikalk/adlc-team-skills --skill team-diagnose -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install tikalk/adlc-team-skills team-diagnose --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/tikalk/adlc-team-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/team/team-diagnose .claude/skills/team-diagnose && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "team-diagnose" agent skill from https://github.com/tikalk/adlc-team-skills/tree/main/skills/team/team-diagnose into .claude/skills/team-diagnose/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-diagnose", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/tikalk/adlc-team-skills/tree/main/skills/team/team-diagnoseType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add tikalk/adlc-team-skills --skill team-diagnose -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install tikalk/adlc-team-skills team-diagnose --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tikalk/adlc-team-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/team/team-diagnose .agents/skills/team-diagnose && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "team-diagnose" agent skill from https://github.com/tikalk/adlc-team-skills/tree/main/skills/team/team-diagnose into .agents/skills/team-diagnose/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-diagnose", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add tikalk/adlc-team-skills --skill team-diagnose -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install tikalk/adlc-team-skills team-diagnose --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tikalk/adlc-team-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/team/team-diagnose .cursor/skills/team-diagnose && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "team-diagnose" agent skill from https://github.com/tikalk/adlc-team-skills/tree/main/skills/team/team-diagnose into .cursor/skills/team-diagnose/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-diagnose", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/tikalk/adlc-team-skills.git --path skills/team/team-diagnose--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add tikalk/adlc-team-skills --skill team-diagnose -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install tikalk/adlc-team-skills team-diagnose --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tikalk/adlc-team-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/team/team-diagnose .gemini/skills/team-diagnose && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "team-diagnose" agent skill from https://github.com/tikalk/adlc-team-skills/tree/main/skills/team/team-diagnose into .gemini/skills/team-diagnose/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-diagnose", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install tikalk/adlc-team-skills team-diagnoseInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add tikalk/adlc-team-skills --skill team-diagnose -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/tikalk/adlc-team-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/team/team-diagnose .github/skills/team-diagnose && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "team-diagnose" agent skill from https://github.com/tikalk/adlc-team-skills/tree/main/skills/team/team-diagnose into .github/skills/team-diagnose/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-diagnose", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add tikalk/adlc-team-skills --skill team-diagnose -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install tikalk/adlc-team-skills team-diagnose --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tikalk/adlc-team-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/team/team-diagnose .opencode/skills/team-diagnose && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "team-diagnose" agent skill from https://github.com/tikalk/adlc-team-skills/tree/main/skills/team/team-diagnose into .opencode/skills/team-diagnose/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-diagnose", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
team-diagnose- GitHub stars
- 141
- Token cost
- ~806 tokens
- SKILL.md length
- 395 words
- Files
- 1
- Skills in repo
- 44
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when the team context did not appear at session start, a skill failed to trigger, the install behaves unexpectedly, or someone asks why a session ran without team rules —…
- The team context did not appear at session start
- SKILL.md covers Overview, When to Use, Core Process and Report format, plus 2 more sections
- Calls bash, pytest and npx
- A skill failed to trigger
What it does
Team Diagnose is an agent skill from tikalk/adlc-team-skills. Use when the team context did not appear at session start, a skill failed to trigger, the install behaves unexpectedly, or someone asks why a session ran without team rules — walks the failure chain with commands and evidence before any conclusion.
Its SKILL.md is about 810 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA. The repository describes itself as: Agent skills for the Agentic SDLC: team lifecycle (team-boot, team-learn, team-init, team-repair), software factory, evals, CDR lifecycle with confidence scoring, and… The licence is MIT.
When your agent uses it
- The team context did not appear at session start
- A skill failed to trigger
- The install behaves unexpectedly
- Someone asks why a session ran without team rules — walks the failure chain with commands and evidence before any conclusion
Example prompts
- “/team-diagnose”
Requirements
- Node.js
What it can do on your machine
Read from SKILL.md and the folder at commit 4c4ad44. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
bashpytestnpx
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Team Diagnose loads about 806 tokens when it runs. Until then it costs about 66 tokens; SKILL.md has 395 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from tikalk/adlc-team-skills at commit 4c4ad44, republished under its MIT licence (© tikalk). 395 words, ~806 tokens.
Download SKILL.mdSave it as
.claude/skills/team-diagnose/SKILL.md (or your agent's skills folder).- name
- team-diagnose
- description
- Use when the team context did not appear at session start, a skill failed to trigger, the install behaves unexpectedly, or someone asks why a session ran without team rules — walks the failure chain with commands and evidence before any conclusion.
team-diagnose
Overview
Evidence-first diagnosis of broken adlc-team-skills wiring. The chain has exactly five links, each checkable with one command — a diagnosis without command output is a guess, and guesses get pasted into bug reports.
Boundary: this repo owns .events.json and the boot scripts' output.
The injection side (dispatchers, generated per-agent plugins) is owned by
adlc-cli — the
docs/event-hook-contract.md file in the adlc-team-skills repo draws the
line. Diagnose up to it, then route.
When to Use
- Team context missing at session start (no
Team Context & Decisionssection). - A rule that should have matched didn't load.
- Install behaves unexpectedly after an update.
When NOT to use: for application bugs unrelated to the team-context chain, or for skill behavior debates (that's a goldset/eval question).
Core Process
Run the checks in order — stop at the first failure, fix, re-run:
| # | Symptom area | Check (run it) | Green means |
|---|---|---|---|
| 1 | Not configured | cat .adlc/init-options.json | A team_ai_directives path that exists |
| 2 | Missing tool | command -v jq | jq on PATH (skills registry needs it) |
| 3 | Broken handler | bash .agents/skills/team-boot/scripts/boot.sh from the project root | The directives index on stdout, wrapped in EXTREMELY_IMPORTANT |
| 4 | Stale install | pytest tests/unit/test_generated_artifacts_sync.py -q (in the skills repo) or compare skills/**/SKILL.md vs .agents/skills/ names | Mirror matches source |
| 5 | Injection side | Generated plugin present and loaded for the agent? | If 1–4 are green and the session still lacks context → adlc-cli's territory — file there with the outputs of checks 1–4 attached |
For "a rule didn't load" specifically: confirm the session began with the index (check 3's content), then check the task actually matched the rule's descriptor — on-demand pull is match-driven, not mind-reading.
Whole-loop check: scripts/acceptance-test.sh scratch-installs and
asserts the chain end-to-end (add --live for a real agent session).
Show full SKILL.md (116 more words)Show less
Report format
For a bug report, include: the failing check number, the command, its
verbatim output, agent name/version, and how the repo was installed
(npx skills add vs adlc-cli). No scrubbed narrative — raw
output.
Red Flags
- Concluding before running a command — every check is one command.
- "Reinstall everything" before reading check 3's output.
- Blaming a skill's content when check 1–3 failed (config, not skills).
- Filing injection-side bugs in adlc-team-skills (check 5 routes them).
All of these mean: run the checks, then report.
Verification
A diagnosis is done when:
- Checks 1–4 each ran with output captured (or 5 routed with evidence)
- The failing link is named with its command output
- The report routes to the owning repo
© tikalk, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/team/team-diagnose of tikalk/adlc-team-skills.
Open the folder on GitHubat commit 4c4ad44
Compare with similar skills
Team Diagnose next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Team Diagnose this skilltikalk/adlc-team-skills | 141 | — | ~806 | Automated safety check: Pass | MIT | |
| Pester Failure AnalysisPowerShell/PowerShell | 56k | — | ~5.1k | Automated safety check: Pass | MIT | |
| Rust TDD Workflowrtk-ai/rtk | 83k | — | ~753 | Automated safety check: Notes | Apache-2.0 | |
| Clawteam DevHKUDS/ClawTeam | 5.5k | 1 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Browser Testing with Chrome DevToolsaddyosmani/agent-skills | 103k | 4 repos | ~3.5k | Automated safety check: Warn | MIT | |
| Apple Container Test RunnerRustPython/RustPython | 22k | — | ~467 | Automated safety check: Pass | MIT |
Similar skills
Rust TDD Workflow
rtk-ai/rtk
Enforces red-green-refactor for Rust work, with idiomatic test patterns, a naming convention and a pre-commit gate of cargo fmt, clippy and test.
Clawteam Dev
HKUDS/ClawTeam
A skill your agent uses when working inside the ClawTeam repository itself: local development, debugging, reviewing, testing, validating multi-agent flows, or checking whether a code change actually…
Browser Testing with Chrome DevTools
addyosmani/agent-skills
Connects an agent to a real Chrome instance through the Chrome DevTools MCP server, so it can inspect the DOM, read console errors and profile performance directly.
Apple Container Test Runner
RustPython/RustPython
Runs RustPython tests inside a Linux container built with Apple's container CLI, so macOS users can compare Linux results with their local ones.
Codex Plugin QA
code-yeongyu/oh-my-openagent
Tests the omo Codex plugin in an isolated CODEX_HOME with a local mock model, proving hooks fired through app-server notifications without touching ~/.codex.
More from tikalk/adlc-team-skills
All 44 skills in this repoTeam Boot
tikalk/adlc-team-skills
A skill your agent uses when a session starts or resumes after compaction (auto via the sessionstart and sessioncompact event hooks) and the team AI directives context — constitution, CDR index…
Architect Clarify
tikalk/adlc-team-skills
A skill your agent uses when ADRs need review, gaps need filling, or ADR status must be approved as Accepted before architecture generation.
Change Clarify
tikalk/adlc-team-skills
A skill your agent uses when reviewing, accepting, rejecting, or deferring ChDRs mined by change-init, validating inferred decisions against their git and issue evidence before promotion to project…
Change Init
tikalk/adlc-team-skills
A skill your agent uses when you want guided mining of git history, structured change-story clustering, or comprehensive rationale recovery before documenting.
Change Publish
tikalk/adlc-team-skills
A skill your agent uses when accepted ChDRs are ready for promotion from drafts to project memory at docs/adlc/memory/chdr/ and the boot-facing chdr.md index needs regenerating.
Evals Analyze
tikalk/adlc-team-skills
A skill your agent uses when evaluation results need triage and loop-closing — spec failures route to deterministic checks or context rules, generalization failures to the evaluator backlog.
Related
Categories
Questions about Team Diagnose
What does Team Diagnose do?
A skill your agent uses when the team context did not appear at session start, a skill failed to trigger, the install behaves unexpectedly, or someone asks why a session ran without team rules —…. Team Diagnose is an agent skill from tikalk/adlc-team-skills. Use when the team context did not appear at session start, a skill failed to trigger, the install behaves unexpectedly, or someone asks why a session ran without team rules — walks the failure chain with commands and evidence before any conclusion.
When should I use Team Diagnose?
Team Diagnose fits situations like: the team context did not appear at session start; A skill failed to trigger; the install behaves unexpectedly; someone asks why a session ran without team rules — walks the failure chain with commands and evidence before any conclusion.
How do I install Team Diagnose in Claude Code?
Run `npx skills add tikalk/adlc-team-skills --skill team-diagnose -a claude-code`. Or copy the skill folder (skills/team/team-diagnose in tikalk/adlc-team-skills) into .claude/skills/team-diagnose in your project. Claude Code loads it when a task matches its description.
How do I install Team Diagnose in Codex?
Run `npx skills add tikalk/adlc-team-skills --skill team-diagnose -a codex`. Or copy the skill folder (skills/team/team-diagnose in tikalk/adlc-team-skills) into .agents/skills/team-diagnose in your project. Codex loads it when a task matches its description.
Can I use Team Diagnose in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add tikalk/adlc-team-skills --skill team-diagnose -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/team-diagnose, .gemini/skills/team-diagnose, .github/skills/team-diagnose and .opencode/skills/team-diagnose in your project.
What does Team Diagnose need to run?
Going by SKILL.md and its folder, Team Diagnose needs the command-line tools its instructions call (bash, pytest and npx). Our summary lists: Node.js.
Does Team Diagnose access the network?
SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.
Is Team Diagnose safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Team Diagnose use?
Team Diagnose is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Team Diagnose use?
About 806 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Team Diagnose?
Skills that share tags, products or a category with Team Diagnose: Pester Failure Analysis (PowerShell/PowerShell, 56k stars), Rust TDD Workflow (rtk-ai/rtk, 83k stars), Clawteam Dev (HKUDS/ClawTeam, 5.5k stars) and Browser Testing with Chrome DevTools (addyosmani/agent-skills, 103k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Team Diagnose?
tikalk (a GitHub organization) maintains it in tikalk/adlc-team-skills, which has 141 GitHub stars. The repository holds 44 skills in this directory. The repository was last updated on October 8, 2026.
Source: tikalk/adlc-team-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.