investigate
Skill2 starsChanged 5 months agoMITView on GitHub
Use when the user wants to follow the connections in the procurement data — a specific supplier, authority, or signing official, or "who wins from many authorities", "who signs these", "what links these companies", network/relationship questions.
129 other projects use a version of this.
Adopted by
Most recently taken up by
- daryaKuto/claude-skillstheir own version, first seen Nov 15, 2026
- Dimon94/dveritytheir own version, first seen Nov 15, 2026
- Dimon94/skillstheir own version, first seen Nov 15, 2026
- lohi-ai/babysittheir own version, first seen Nov 14, 2026
- Blakeem/aipromptguide-workflowstheir own version, first seen Nov 12, 2026
- charles-adedotun/sre-plugintheir own version, first seen Nov 8, 2026
Used with
Projects with it also use pair-agent, plan-devex-review and 10 more.
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.
seek888Skillpair-agent
Pair a remote AI agent with your browser. One command generates a setup key and prints instructions the other agent can follow to connect. Works with OpenClaw, Hermes, Codex, Cursor, or any agent that can make HTTP requests. The remote agent gets its own tab with scoped access (read+write by default, admin on request). Use when asked to "pair agent", "connect agent", "share browser", "remote browser", "let another agent use my browser", or "give browser access". (gstack) Voice triggers (speech-to-text aliases): "pair agent", "connect agent", "share my browser", "remote browser access".
Also in 10 projects that use this
seek888Skillplan-devex-review
Interactive developer experience plan review. Explores developer personas, benchmarks against competitors, designs magical moments, and traces friction points before scoring. Three modes: DX EXPANSION (competitive advantage), DX POLISH (bulletproof every touchpoint), DX TRIAGE (critical gaps only). Use when asked to "DX review", "developer experience audit", "devex review", or "API design review". Proactively suggest when the user has a plan for developer-facing products (APIs, CLIs, SDKs, libraries, platforms, docs). (gstack) Voice triggers (speech-to-text aliases): "dx review", "developer experience review", "devex review", "devex audit", "API design review", "onboarding review".
Also in 13 projects that use this
ShreyRaviSkilllanding-report
Read-only queue dashboard for workspace-aware ship. Shows which VERSION slots are currently claimed by open PRs, which sibling Conductor workspaces have WIP work likely to ship soon, and what slot /ship would pick next. No mutations — just a snapshot. Use when asked to "landing report", "what's in the queue", "show me open PRs", or "which version do I claim next". (gstack)
Also in 7 projects that use this
ayudaySkillsetup-deploy
Configure deployment settings for /land-and-deploy. Detects your deploy platform (Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions, custom), production URL, health check endpoints, and deploy status commands. Writes the configuration to CLAUDE.md so all future deploys are automatic. Use when: "setup deploy", "configure deployment", "set up land-and-deploy", "how do I deploy with gstack", "add deploy config".
Also in 14 projects that use this
ramybarsoumSkilldocument-release
Post-ship documentation update. Reads all project docs, cross-references the diff, updates README/ARCHITECTURE/CONTRIBUTING/CLAUDE.md to match what shipped, polishes CHANGELOG voice, cleans up TODOS, and optionally bumps VERSION. Use when asked to "update the docs", "sync documentation", or "post-ship docs". Proactively suggest after a PR is merged or code is shipped.
Also in 18 projects that use this
GeiserXSkilldocs-loop
Use when the user asks to audit docs, check documentation for stale claims, or verify docs against the code.
Also in 3 projects that use this
- +1 more from seek888
Other versions129 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 129
- recharts/recharts★ 28ksame name
- gitkraken/vscode-gitlens★ 10ksame name
- vercel/eve★ 5.9ksame name
- rilldata/rill★ 3ksame name
- DenchHQ/DenchClaw★ 1.7ksame name
- DenchHQ/ironclaw★ 1.7ksame name
- ceedaragents/cyrus★ 903same name
- cyrusagents/cyrus★ 902same name
- rommapp/argosy-launcher★ 737same name
- mr-daedalium/ostack-saas★ 108same name
119 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.
In this repository4 other files it gives its agents.
- build-corpusSkill
- detect-red-flagsSkill
- pull-dataSkill
- write-briefSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 116 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
Start from a lead (from detect-red-flags) or a name the user gives you.
- Very specific: line 23
Use cross to find suppliers active across many authorities, and link to find who shares authorities with a target supplier (possible …
- Very specific: line 29
Read the source decision text for context: node lib/extract.mjs --in=data/contracts.jsonl then read corpus/<id>.md.
“Common” is measured: kept by at least 6 in 10 of the 116 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
Investigate the connections
The whole point: turn a list of awards into a network of suppliers ↔ authorities ↔
signing officials. Use lib/connect.mjs (reads data/contracts.jsonl + data/awards.jsonl).
node lib/connect.mjs supplier 800591565 # one supplier: every authority, signer, CPV, total
node lib/connect.mjs authority Ιπποκρατειο # an authority: top suppliers + signers
node lib/connect.mjs signer Καρουζος # one official: their whole award network
node lib/connect.mjs cross --min=3 # suppliers winning from ≥3 authorities (connected players)
node lib/connect.mjs link 800591565 # 2-hop: a supplier → its authorities → their OTHER suppliersHow to investigate well
- Start from a lead (from detect-red-flags) or a name the user gives you.
- Pull the supplier and the signer profiles — the recurring official is often the thread.
- Use
crossto find suppliers active across many authorities, andlinkto find who shares authorities with a target supplier (possible related vendors). - Resolve identities: the same company can appear under spelling variants (Greek vs Latin,
"ΑΕ" vs "AE"). Group by ΑΦΜ, not name. Use
node lib/vies.mjs <ΑΦΜ>to get the canonical legal name, and — once a ΓΕΜΗ key is configured —node lib/gemi.mjs vat <ΑΦΜ>to pull owners / board members, which is what truly links companies to people and officials. - Read the source decision text for context:
node lib/extract.mjs --in=data/contracts.jsonlthen readcorpus/<id>.md.
Always
- Frame as leads, not accusations. Cross-authority activity and repeat signers have legitimate explanations; the user must verify against the documents and seek comment.
- Cite the evidence links for every claim.
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.

