market-intel
Skill2 starsChanged 4 months agoMITView on GitHub
Research and deliver structured intelligence on competitors, contracts, tenders, and market movements relevant to a large infrastructure services enterprise's business.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- DaizeDong/market-inteltheir own version, first seen Oct 16, 2026
- HKUDS/AI-Tradertheir own version, first seen Oct 8, 2026
- Dangooy/tianji-skillstheir own version, first seen Sep 26, 2026
- haidrrrry/Ai-trader-protheir own version, first seen May 22, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- HKUDS/AI-Trader★ 23ksame name
- haidrrrry/Ai-trader-pro★ 15same name
- Dangooy/tianji-skills★ 11same name
- DaizeDong/market-intel★ 4same name
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 repository37 other files it gives its agents.
- commercial-insightSkill
- data-requestSkill
- scenario-modelSkill
- duckdbSkill
- intelligence-internal-commsSkill
- sql-reviewSkill
- xlsxSkill
- docxSkill
- pdfSkill
- pptxSkill
- theme-factorySkill
- utility-markitdownSkill
- thinkcellSkill
- clevel-reviewSkill
- exec-commsSkill
- partner-reviewSkill
- working-constructSkill
- route-taskSkill
- pm-customer-journeySkill
- pm-exec-onboardingSkill
- pm-problem-statementSkill
- pm-proto-personaSkill
- pm-storyboardSkill
- pm-user-storySkill
- kanban-curateSkill
- epic-builderSkill
- exec-summarySkill
- steerco-packSkill
- program-trackerSkill
- weekly-reviewSkill
- book-deskSkill
- draw-excalidraw-diagramSkill
- mcp-builderSkill
- notion-workboardSkill
- smartsheetSkill
- utility-transcribeSkill
- writing-humanizerSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
5
Distinctive
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
- Distinctive: line 11
When Jacob names a competitor (Broadspectrum, Downer, Spotless, UGL, Programmed, Serco, Sodexo, Transdev, John Holland) or a specific …
- Distinctive: line 27
If the request spans more than one mode, note it and structure the output accordingly.
- Distinctive: line 33
Always search the web. Cover these sources:
- Distinctive: line 42
Search broadly first, then drill into specifics.
- Very specific: line 100
Use the venv at <workspace>/.venv and inline heredoc via Bash.
- Distinctive: line 124
Flag staleness: If a source is older than 90 days, note it.
“Common” is measured: kept by at least 6 in 10 of the 3 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
Skill: Market Intelligence
When to Invoke
- "who won [contract/tender]", "what's [competitor] doing", "market intel on [topic]"
- "competitor analysis", "contract award", "tender intelligence", "work-winning"
- When Jacob names a competitor (Broadspectrum, Downer, Spotless, UGL, Programmed, Serco, Sodexo, Transdev, John Holland) or a specific contract/tender
- "what are we competing against", "market update", "pipeline intel"
Step 1 — Classify the Request
Identify which mode applies before researching:
| Mode | Description |
| Competitor profile | Deep dive on a specific company |
| Contract/tender intel | Specific contract award or upcoming tender |
| Market scan | Broader sector or industry update |
| Work-winning context | Intelligence to support a bid or client conversation |
If the request spans more than one mode, note it and structure the output accordingly.
Step 2 — Research
Always search the web. Cover these sources:
- ASX announcements & investor docs — for listed entities: DOW, CIMIC, Ferrovial, PERSOL Holdings
- Tender portals — AusTender (Commonwealth), Buy NSW, Tenders VIC, QTenders, SA Tenders, WA Buy, NZ GETS
- Industry publications — Infrastructure Magazine, Utility Magazine, Roads Australia, AMCA, Defence Connect, The Fifth Estate
- News & press — Company newsrooms, AFR, The Australian, Reuters, LinkedIn announcements
- Government budgets and policy — Infrastructure Australia pipeline, NDIS/defence budget statements, state infrastructure plans
- Contract registers — where agencies publish awarded contracts publicly
Search broadly first, then drill into specifics. Note the date of each source.
Step 3 — Structure the Output
Competitor Profile
| Section | Content |
| Company snapshot | Revenue, headcount, sectors, ownership structure (listed/private/subsidiary) |
| Recent wins | Contract awards in the last 12 months — values where disclosed |
| Recent losses | Contracts lost, not renewed, or retendered |
| Strategic moves | M&A activity, restructures, leadership changes, new market entries or exits |
| Relevance to the enterprise | Where they compete head-to-head; where they don't |
| Strengths / Vulnerabilities | What they do well; where the enterprise has a credible advantage |
Contract / Tender Intel
| Section | Content |
| Contract details | Name, client, estimated value, duration, scope of services, location |
| Award details | Winner, award date, any public commentary from client or awardee |
| Known bidders | Entities known to have bid (from news, announcements, or market intelligence) |
| Scope analysis | Services in scope, sectors covered, geographic footprint |
| Enterprise relevance | Whether the enterprise bid, could have bid, or should track the renewal |
| Comparable contracts | Similar contracts the enterprise holds or adjacent opportunities in the pipeline |
Market Scan
| Section | Content |
| Key movements | Contract awards, M&A, leadership changes, regulatory changes in last 90 days |
| Pipeline | Known upcoming tenders, contract renewals, or government procurement events |
| Trends | Pricing direction, consolidation signals, technology adoption, policy changes |
| Enterprise implications | What this means for positioning, strategy, or specific business units |
Work-Winning Context
Lead with: what does the client care about, who else is likely bidding, and what is the enterprise's differentiated position. End with a recommended angle or emphasis for the bid narrative.
Step 4 — Deliver
In-Conversation (default)
Present the full structured output in markdown. Always include:
- Source citations (URL or publication + date) for every material claim
- "As at [date]" flag on time-sensitive intelligence
- A "So what" closing paragraph: what the enterprise should do with this information
Document Output (if Jacob requests)
Generate a Word document using python-docx (NOT docx-js — it won't open in Word for Mac).
Save to: 4 - Projects/[topic-kebab]/[YYMMDD]_Market_Intel_[Subject].docxUse the venv at <workspace>/.venv and inline heredoc via Bash. Structure: cover page → executive summary → sections per the relevant output format above → sources appendix.
Company Context (Reference)
| Field | Detail |
| Company | A large ASX-listed infrastructure services enterprise |
| Revenue | ~$6B AUD |
| Sectors | Defence & Social Infrastructure, Telecommunications, Transport, Infrastructure Services |
| Key competitors | Broadspectrum (Ferrovial), Downer (DOW), Spotless (Downer sub), UGL (CIMIC), Programmed (PERSOL), Sodexo, Serco, Transdev, John Holland |
| Key clients | Department of Defence, a national network client, a telco client, state transport agencies, water utilities |
| Geography | Australia and New Zealand |
| Currency | AUD |
| Brand | Brand-adaptable output (bring your own theme) |
Rules
- Cite every claim. URL, publication name, and date. No exceptions.
- Never fabricate contract values, award details, or bid outcomes. If not publicly available: "not disclosed" or "not confirmed."
- Distinguish confirmed vs. speculated. Label rumours or inferred intelligence explicitly.
- Flag staleness. If a source is older than 90 days, note it.
- Be specific about action. End every output with what the enterprise should DO, not just what the market IS doing.
- Tone: Analyst-grade. Direct. No padding, no hedging unless uncertainty is genuine.
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.