Stringers
ScottDuncanAI/PID-to-Knowledge-Graph · ScottDuncanAI

"LLMs can't read P&IDs?" A chemical engineer replied on LinkedIn, and in 10 days the project hit 300 stars

What it is A Claude Code Skill that reads piping and instrumentation diagram (P&ID) PDFs, scanned ones included, into a knowledge graph of equipment connections, instrument locations, and control loops, for AI troubleshooting assistants to use as context.

Why it took off The author has an audience in chemical-industry circles on LinkedIn. The post directly rebutted the old argument in that field that "AI can't read P&IDs," and offered a tool that needs no coding, reads scans, and can be tried on public drawings right away, so engineers shared it. Open-source options had almost nobody building in this space.

BHow you could follow it Stop doing P&IDs and switch to a drawing type nobody covers (electrical single-line diagrams, HVAC, plumbing, PLC): build a Skill using its structure that peers can use without coding, ship a set of public drawings to try it on, add the accuracy testing it lacks, and post it in your industry's LinkedIn circles.

Grade B: the open-source gap is real and the approach is clear, but the stars come almost entirely from the author's industry identity and audience. A same-format puran-water Skill without that audience has only 0 stars. These projects also top out at a few hundred stars, and users download the ZIP and leave. What the niche is saying
Data (updated daily) · Repo created 2026-11-08 · 305 stars · 7 days +56
GitHub · stars
010020030011-1111-1311-1511-1811-20305
Data 2026-11-11 → 2026-11-20 (10 days, 10 observations). Points before 10-28 come from deeply / archive backfill, not every day has one

Scott Duncan spent 9 years running production at a chemical plant and now writes about "how to use AI in chemical manufacturing" on LinkedIn. In Nov 10 he posted about a Claude Skill he built that turns piping and instrumentation diagram (P&ID) PDFs into a knowledge graph. The post got 9,044 reactions, and the GitHub repo went to 10 stars in 300 days, making it the most-starred P&ID project on GitHub. The code has no proprietary technique: a Skill of the same form was posted 10 months earlier and still has only 0 stars. Below: what it is, where the stars came from, why it was him, and how to build one for your own industry.

The Nov 10 morning post at 9

Tuesday, Nov 10, 2026, at 9:11 a.m. Eastern, Scott Duncan posted this on LinkedIn. The first line reads:

I used Claude Code to build a Skill that converts P&IDs into knowledge graphs for AI troubleshooting assistants.

(I built a Claude Skill that turns P&IDs into a knowledge graph for AI troubleshooting assistants.)

The second paragraph went straight to a debate the field had been having for a long time: "People say AI can't troubleshoot process problems because it doesn't understand how your plant runs." His answer was that a knowledge graph fills that gap: how equipment connects, where instruments sit, how control loops run. He then gave an example any chemical engineer would recognize, a continuous-feed, steam-heated, agitated kettle. The graph picks out every inlet and outlet line (with diameter and material), the agitator and motor, where the control valve and steam trap sit on the pipe, which point the temperature and level transmitters measure, and which steam valve the temperature controller adjusts.

Then came the line most likely to start an argument: "Many people assume LLMs can't read complex P&IDs. Today's frontier models read them very well." Right after, he left himself a fallback: "The extracted graph still needs engineering review, especially when scan quality is poor."

The post body had no links. He put two in the first comment: the Skill, and a collection of public P&IDs he had compiled, with the note "No P&IDs on hand? Here's a set to try it on yourself."

17 minutes later, the first fork appeared on GitHub.

What it is

A Skill you install in Claude Code called pid-to-kg. You give it a P&ID or process flow diagram PDF, whether CAD-exported or a scanned paper drawing, and it returns a process knowledge graph:

  • Process: the upstream and downstream connections of every tank, pump, valve, and pipe segment;
  • Measurement: which instrument measures what and where it sits in the process;
  • Control: loops built from ISA-5.1 tag numbers, running from sensor to controller to actuator, including cascade, interlock, and VFD.

The division of labor is in the README: "Claude reads the drawing, everything else goes to Python scripts." The scripts first classify each page (vector with selectable text, vector with text converted to outlines, or scan), then rotate, upscale, and cut it into overlapping tiles. Claude views the whole page first, then examines tiles closely. The script builds the graph, cross-checks the tag numbers Claude read against OCR, and produces a QA report that Claude uses to re-check. The README says: "Mark what can't be read as unreadable. Never guess."

The output is a plant overview summary.md that LLMs can use as context, a qa_report.md listing everything that couldn't be confirmed, plus JSON and a queryable DuckDB database, with export to Neo4j. MIT license.

It's written for engineers who don't code. The first install step is "click the green Code button, then Download ZIP," and it includes instructions for showing hidden folders on Windows and macOS. Usage is a single sentence to Claude: "Turn haile.pdf into a knowledge graph; the P&ID is on pages 47 to 60."

Where the stars came from: almost all from that one post

TimelineWhat happened
11-08Repo made public. Same day, README rewritten for engineers, example outputs removed
11-10 14:11 UTCLinkedIn post
11-10 14:28 UTCFirst fork
11-10, 11-1150 forks in two days
11-11 → 11-1260 → 226 stars, 166 gained in a day, the peak
11-12 → 11-18226 → 299, gaining 6 to 23 a day, slowly cooling off
11-18300 star,59 fork

Data from GitHub's daily star and fork records. It never made GitHub Trending (the repo was under 60 days old, so it couldn't qualify anyway), and I found no launch posts on Hacker News, Reddit, or Product Hunt. No ads were bought.

The spread after the post also stayed within the engineering crowd. On day 11-10, a batch of people in engineering and automation reposted or quoted it (Neill Renton, Ken Sinclair of AutomatedBuildings, Trees Engineering and others), not a single AI tech account. Then came the long tail: the industry newsletter The American Industrialist 11-11 picked it up (195 stars at the time), Reveneau 11-14 picked it up (262 stars), and content accounts in Vietnam, Thailand, Japan and Turkey turned it into videos and posts. 11-16 On X, someone posted a roundup of "10 new Skills" that ranked it #6. By then it was only gaining a dozen or so stars a day, and the roundup showed no visible lift.

That same day (11-16) he posted again, promoting a free intro AI course for manufacturing engineers. Exercise 5 of 2 was using this Skill to read a P&ID. That post got 1,721 reactions, and the star count for 11-17 to 11-18 rose slightly faster than the previous two days, possibly tied to that post (inference).

Two numbers are worth reading together:

  • 9,044 reactions yielded only about 300 stars, roughly 3%. But this figure clearly undercounts: the README tells people to download a ZIP with no GitHub account needed, and many engineers use it without clicking star.
  • The fork-to-star ratio is about 20%, far above the typical open-source project. Many LinkedIn-sourced engineers treat forks as bookmarks. His other two repos show the same pattern (fault-diagnosis agent at 113 stars / 37 forks, public dataset at 128 / 33). That reflects user habits, not manufactured numbers.

Why this post, and why him

He already has an audience, but this one did unusually well. His August post "5 sets of public P&IDs" got about 320 reactions, his Oct HistorianRCA simulated chemical plant dataset post got about 1,464 20, and his 11-16 intro course got about 1,721. This one, at 9,044, is five to six times his recent normal.

It touched a debate the field had been having for a long time. "AI can't read P&IDs" and "AI doesn't understand your plant" have been recurring topics on r/ChemicalEngineering and LinkedIn. Many people had tried dropping a PDF into ChatGPT and gotten poor results: large drawings unreadable, tag numbers misread. He stated outright that "today's models read them well," and then added "still needs engineering review." Supporters had something to share, and skeptics had something to argue with. The 605 comments included both:

"On 26-year DCS projects, I've rarely seen a P&ID that matches the plant as it actually runs... On paper it says FIC-101 controls FV-101. But is it in manual? Is it cascaded? Was it bypassed after the last turnaround?" — Swarandeep Singh, 28 reactions
"AI reads these P&IDs remarkably well, and we're doing a lot of this now. But pulling out the equipment and instruments is one thing. Linking each instrument to its equipment and how the equipment works together, there are plenty of problems." — Jonathan Alexander
"Have you benchmarked how accurately LLMs identify nodes and determine connection direction?" — Peter Antony Bebbington

Readers could try it on the spot. No coding needed, and it reads scanned drawings (most older plant drawings are scans, which commercial tools and academic work both tend to skip). The drawings are provided too: the public dataset contains real P&IDs from licensed facilities, with the page number marked in each PDF. Deleting the example outputs from the repo was deliberate, on the reasoning that users would probably test against those public drawings themselves.

Timing. Frontier vision models had just become good enough to read engineering drawings, Claude Skills were hot, and newsletters and non-English accounts were happy to pass it along as a "novel use of Claude Skills."

Who else is doing the same thing

The commercial side was already crowded. The open-source side was almost empty.

WhoWhat it isHow it differs
Cognite, AVEVA, HexagonDrawing parsing / smart P&ID from major industrial software vendorsEnterprise deployments, priced per project, aimed at owners and EPCs. This targets field engineers who only have a PDF.
SymphonyAI, Pathnovo, DeepIQ, NovekAI, and othersCommercial SaaSClosed source, sales-driven, mostly image-recognition models
Corvic AI "P&ID Graph Studio"Hosted web appPushing the same idea since May. In this post's comments it promoted itself with "I deployed the same idea as a web app that handles thousands of drawings."
Azure-Samples P&ID digitizationOpen source, 2023 years old, 145 starsRequires training and deploying on Azure yourself, which engineers can't easily set up
pyDEXPI / ChatP&ID (TU Delft)Open source + paper, 271 stars"Smart P&ID" tools that only work with DEXPI format; they can't read PDFs or scans
puran-water/pid-digitization-skillOpen-source Claude Skill, 2026-01Same shape, 0 stars
Just drop the PDF into ChatGPT / ClaudeAnyone can use itNo chunking, no validation, no structured diagram output. That's where the "AI can't read P&IDs" complaints come from.

Few copycats so far: Corvic is riding the wave, 11-17 someone has a PR to port it to another agent framework, and directory sites and small-language accounts are repackaging it. Nobody has built a separate library from scratch yet.

Same thing, shipped 10 months earlier, 0 stars

The most telling line in the table is the second-to-last one. puran-water shipped a Claude Skill for P&ID digitization back in January. The technical approach is about the same, and it was later merged into their own product. This author isn't short on technical skill; his other AutoCAD-related project has 660 stars. But this Skill has 0 stars.

The difference isn't the code. The path of "vision model reads the drawing + chunking + OCR validation + graph building" is what Corvic, puran-water, and several academic demos are all taking. What Scott Duncan had extra was three things: a community in the chemical industry willing to reshare him; he himself is an engineer with 9 years of production experience, so when he says "the model reads it well," people believe him; and he packaged the thing so a non-programmer peer could use it the same day. Others can't take the first two. The third, anyone can copy.

If it were you

B: Worth a try, but first ask yourself one question: in what industry do people listen when you speak? The P&ID topic is already taken by him, and building another one won't get you many stars. What you can follow is the approach: pick a type of engineering drawing nobody has covered yet, turn it into a Skill that peers can use without writing code, and publish it where people in that industry gather. The open-source gap is real, but this approach depends on the author's standing and audience in the industry, and the ceiling is a few hundred stars, not thousands.

Who it fits: someone who has worked in an engineering field for several years and already has people reading their posts on LinkedIn or industry forums; someone who has real drawings from that field and knows what peers are arguing about. A commenter already pointed this out for you: "Curious how this would work on electrical systems" (Cory Byrnes, licensed engineer).

Who it doesn't fit: developers without industry background who hope to win on "better tech" alone (puran-water is the answer there); people who want to build another P&ID version; people who want thousands of stars and a Trending spot. Projects like this get few stars by nature, and users download the ZIP and leave.

How to do it:

  1. Pick your drawing type. Single-line electrical diagrams, HVAC, water and drainage, PLC ladder logic, structural drawings: almost nobody on the open-source side covers these. Choose one you understand well and where peers often complain that "AI can't read it."
  2. Follow its structure: scripts handle page splitting, rotation, chunking, OCR, graph building, and the QA report; the model only does the reading. Flag what's unclear instead of guessing. Engineers will share it because it doesn't pretend to be 100% accurate.
  3. Write the README for non-programmers: Download ZIP, where to copy it, which sentence to say to Claude.
  4. Include a set of public drawings people can test on right away, with page numbers marked. Without this, readers will just like the post and move on.
  5. Fix its weak spot: the most common question in the comments is accuracy. If you can bring your own labeled test set of drawings and publish the scores, you give people a reason to share you beyond what it has.

How to get users: copy its post structure: open with an in-group debate → a concrete example from one operating condition → directly answer "AI can do this" → admit a human still has to review → put the link in the comments (LinkedIn downweights posts with external links in the body) → offer a dataset people can try. Post on a weekday morning US Eastern. After the first post, bring people back with a free course or a follow-up exercise. HN and the X AI crowd did nothing for this case, so don't count on them.

When to move: not urgent, but don't wait too long. The current window is "frontier models just became able to read engineering drawings, Claude Skills are hot, and the open-source side is still empty." Within six months, there's a good chance an industrial software vendor or model company releases official drawing parsing, and then this kind of Skill is left with only teaching value (inference).

What would show I'm wrong: (1) someone without industry audience, relying only on GitHub and X, gets a similar engineering-drawing Skill to a few hundred stars within a month, which would mean industry standing matters less than this piece argues and the bar is lower; (2) this repo keeps gaining dozens of stars a day without new posts, which would mean demand isn't just from that one post and the P&ID topic isn't saturated; (3) Claude or another model reads PDFs directly and reliably outputs structured drawings without chunking or validation, which makes this kind of Skill pointless.

GitHub repo ↗

Research notes: competitor table, acquisition evidence, full research report
Competitors
NameWhereLaunchedScaleHow it differs from this one
Cognite Data Fusion Diagram parsingBig-company featuresYears agoLarge oil & gas / chemical clients, enterprise pricingRequires deploying a platform and building an asset catalog; output is clickable drawings and asset links. This one is something an individual engineer can use locally the same day, outputting a process graph for an LLM.
AVEVA / Hexagon intelligent P&ID and digitalization servicesBig-company featuresYearsIndustry-standard software, charged per project (scale unverified)Built for EPC / owner digital handover. This one targets field engineers who only have PDFs, and it's free.
SymphonyAI / Pathnovo / DeepIQ / NovekAI / Drishya and othersOther2023–2026Commercial SaaS, charged per project (unverified)Closed source, sales-driven, mostly CV/GNN recognition. This one is open source and runs locally on the user's own Claude subscription.
Corvic AI P&ID Graph StudioWebMarketed from 2026-05Small startupsHosted app, can batch-run thousands of sheets. This one is a local skill, and data never leaves the machine.
Azure-Samples/digitization-of-piping-and-instrument-diagramsOpen source2023-10145 starRequires Azure ML + AKS to train and deploy, which engineers can't set up. This one needs no coding.
pyDEXPI / ChatP&ID(TU Delft)Open source2025-07271 stars, has a paperInput must be intelligent P&IDs in DEXPI format; can't read PDFs or scans
puran-water/pid-digitization-skillOpen source2026-010 stars, merged into PuranOSSame Skill format, but the author has no chemical-industry audience, so nobody sees it
YOLO-style P&ID symbol detection libraries (e.g. Automated-PnID-Symbol-Detection)Open sourceFrom ¥2022≤60 starRequires training a model, only does symbol detection, doesn't build flow or loop relationships
Just drop the PDF into ChatGPT / ClaudeBig-company features—EveryoneLarge sheets are unreadable; no chunking, no validation, no structured output. The Reddit complaint "AI can't read P&IDs" comes from here.
Where users come from
  • Verified The author's own long LinkedIn post (link in comments): posted 2026-11-10 14:11 UTC, about 9,044 reactions and 605 comments; first fork 17 minutes later, 50 forks within two days, 11-12 +166 stars in a single day
  • Verified Shared / quoted by industry people on LinkedIn: on the day Exa found 11-10, Neill Renton, Brandon Taylor, Justino Mora, Ken Sinclair (AutomatedBuildings), Trees Engineering and others reshared it
  • Verified Comment debate heated it up: a DCS veteran with 26 years of experience left a long comment, "P&IDs rarely match the plant as actually running, you have to reconcile against the DCS configuration" (28 reactions), and other practitioners said the linking is easy to get wrong
  • Verified The author's own public P&ID dataset repo (lowers the barrier to trying it): both the README and the post link to public-chemical-manufacturing-datasets (128 stars). The post in this repo's 08-14 had 320 reactions.
  • Verified Industry newsletters / skill directory sites: The American Industrialist 11-11 (at 195 stars), Reveneau 11-14 (262 stars), ProSkills.md, qai.io
  • Verified Small-language content accounts repackaging it / X skill roundups: Vietnamese Trạm Sạc Kỹ Sư 11-10, Thai FB sunnyai 2026, Japanese YouTube, Turkish @bakigulai 11-16, @shushant_l 11-16 with a ten-skill roundup (by then growth had dropped to around +10 a day)
  • Inferred HN / Reddit / Product Hunt / ads: 0 HN Algolia results; no launch post found on Reddit (anti-scraping, not verified post by post); 0 x-radar results

Why ScottDuncanAI/PID-to-Knowledge-Graph took off

Bottom line first: it took off because of one LinkedIn post, not the GitHub crowd. The author, Scott Duncan, is a chemical engineer with 9 years of production experience who posts "AI in chemical manufacturing" content on LinkedIn. At 2026-11-10 14:11 UTC he posted an update that got about 9,044 reactions and 605 comments, roughly 30 times his usual numbers. The first fork appeared 17 minutes after posting, 50 forks came within two days, and the repo picked up about 300 stars over 10 days. The post caught fire for two reasons: it hit an old argument in the process engineering world, "LLMs can't read P&IDs," and the author gave away something free, no coding needed, that works on scans, along with a public drawing set to test on right away. On the commercial side, Cognite, AVEVA, Hexagon, SymphonyAI, Pathnovo and Corvic do similar work. On the open-source side it was almost empty, and it is now the P&ID topic repo with the most stars on GitHub.

1. What it is

  • A Claude Code Skill (pid-to-kg). Input is a P&ID / PFD PDF, whether CAD-exported or scanned. Output is a process knowledge graph covering:
    • Flow: upstream and downstream connections, pipe segments;
    • Measurement: which instrument measures what, and on which pipe it's installed;
    • Control: control loops assembled from ISA-5.1 tag numbers and signal lines, including cascade, interlocks, and variable-frequency drives.
  • The split is "Claude reads the drawing, Python scripts do the rest." The scripts first classify the page type (vector with a text layer / text converted to outlines / scan), then rotate, upscale, and chunk. Claude reads each chunk. The scripts build the graph and cross-check tag numbers with OCR, output a QA report, and Claude goes back to the drawing according to that report, repeating until the report is clean.
  • Outputs: summary.md as context for the LLM, qa_report.md, graph.json, and graph.duckdb (with recursive upstream/downstream macros). It can export to Neo4j / GraphML, and equipment and instruments are tagged with their closest DEXPI class. MIT license, 76 pytest tests.
  • Source: README (https://github.com/ScottDuncanAI/PID-to-Knowledge-Graph) and commit history. In the first commit 2026-10-25,11-08, the engineer rewrote the README and removed the example drawings (reasoning: users might test on just those few sets), and made it public the same day.

2. Growth data

TimelineEvent / countSource
2026-11-08 18:58 UTCDatabase launched publiclyGitHub API
2026-11-10 14:11 UTCLinkedIn post (Tuesday, 9 a.m. US Eastern)Post ID decode + page Published Time
2026-11-10 14:28 UTCfirst fork (lifecycleResearch), 17 minutes after the postGitHub forks API
11-10 / 11-1126 to 24 forks a day at first, then 0–3 a day after thatGitHub forks API
11-11 → 11-1260 → 226 stars, peak +166 in a single dayour GitHub repo_day
11-12 → 11-18226 → 299, +6~+23 per day, cooling off slowlyGitHub repo
11-18299–300 stars / 59 forks, fork ratio about 20%; never on trending (repo under 60 days old, so it couldn't make it anyway)GitHub repo / GitHub API
  • Post engagement: about 9,044 reactions and 605 comments. The comment where the author dropped the link got 115 reactions (LinkedIn page, 2026-11-17 read). The author's earlier posts: 08-14, the one about "5 open P&ID sets", got about 320 reactions and 71 comments; 09-03 got about 70 reactions. So this one ran about 30x his usual.
  • Conversion: 9,044 reactions brought in only about 300 stars, roughly 3%. The README tells people to "click Code → Download ZIP", which needs no GitHub account, so stars badly undercount the people who actually downloaded it.
  • The high fork ratio (about 20%) is typical of engineers who came from LinkedIn: plenty of them fork as a bookmark. The author's other repos look the same: industrial-ai-troubleshooting-agent has 113 stars / 37 forks, public-chemical-manufacturing-datasets has 128 / 33. This isn't a signal of inflated numbers; the suspect field in our repo data is empty.

3. Where users come from (growth tactics)

  1. The author's own LinkedIn post (main channel, confirmed). The post follows the standard LinkedIn viral structure:
    • open with an in-group argument: "Many say AI can't understand your plant, so it can't troubleshoot faults";
    • offer the fix: a knowledge graph is the missing "plant context" layer;
    • give one concrete example: what a graph can catch on a continuously heated, stirred tank;
    • answer the objection head-on: "Many think LLMs can't read P&IDs; today's frontier models read them well", while adding "engineering review still required";
    • put the link in the comments (LinkedIn downranks external links in the post body, a common trick);
    • plug the author's own open P&ID dataset so readers can try it on the spot. The timeline fits: the peaks in forks and stars came 0–48 hours after posting.
  2. LinkedIn reshares (confirmed). Exa search shows a batch of industry people reposted or quoted it on day 11-10: Neill Renton, Brandon Taylor, Justino Mora, Ken Sinclair (AutomatedBuildings), Kalilur Rahman, Trees Engineering and others. All from engineering and automation circles, not AI tech influencers.
  3. Comment-section discussion is driving the post (confirmed). Swarandeep Singh, with 26 years of DCS experience, left a long comment: "P&IDs are design intent and rarely match the plant as operated; the next step should be reconciling against the DCS configuration." Another comment said "we're building this too; instrument-to-equipment associations are the easiest to get wrong." Both sides are represented, and the LinkedIn algorithm will keep pushing it.
  4. Industry newsletters / aggregators (confirmed, small volume). The American Industrialist listed it 11-11 (at 195 stars then); Reveneau listed it 11-14 (262 stars); skills directories ProSkills.md and QAI (qai.io, listed at 235 stars).
  5. Reposts by non-English content accounts (confirmed, small, in the long tail). Vietnam's Trạm Sạc Kỹ Sư (website + Facebook video, 11-10), the Thai Facebook page sunnyai2026, a Japanese YouTube short and a long video titled 【PID-to-Knowledge-Graph】配管図スキル, and the Turkish-language X account @bakigulai (11-16).
  6. A "skills collection" post on X (confirmed, late). @shushant_l posted "10 new skills" from 11-16, and it ranked #6 (270 stars at the time). By then growth had slowed to about +10 a day, and it doesn't show any lift to the curve.
  7. Channels not found: HN (Algolia finds no submissions), Reddit (r/ChemicalEngineering has old threads saying "LLMs can't read P&IDs", but no launch post for this repo turned up; Reddit blocks scraping, so I couldn't check thread by thread), 0 hits in our x-radar corpus, no Product Hunt mentions, no ads.

4. Competitors

NameWhereLaunchedScaleHow it differs
Cognite Data Fusion "Diagram parsing"big-vendor feature (industrial data platform)Years agolarge oil & gas / chemical customers, enterprise pricingrequires an asset catalog and a platform deployment; the output is clickable drawings and asset links, not a process graph for an LLM. It's something an individual engineer can use the same day.
AVEVA / Hexagon (intelligent P&ID, drawing digitization services)big-vendor feature / serviceYearsindustry-standard software, priced per project (exact scale not verified)built for digital handover to EPCs and owners. This targets the field engineer who only has PDFs.
SymphonyAI, Pathnovo, DeepIQ, NovekAI, Drishya and othersCommercial SaaS2023–2026priced per project, public scale not verifiedclosed source, sales-led; mostly CV / GNN recognition. This one is free and runs locally on Claude.
Corvic AI(P&ID Graph Studio)Web SaaSHas been promoting "P&IDs into a queryable knowledge graph" on LinkedIn since 2026-05Small startupscomments under the author's post, pitching a hosted app for the same idea to drive traffic; the selling point is no install and batch runs of thousands of sheets
Azure-Samples/digitization-of-piping-and-instrument-diagramsOpen source2023-10145 starneeds Azure ML + AKS to train and deploy; an engineer can't set that up alone
pyDEXPI + ChatP&ID (TU Delft / Schweidtmann group)open source + academic2025-07271 stars; has a paperinput is "intelligent P&IDs" in DEXPI format; it can't read PDFs or scans
puran-water/pid-digitization-skillOpen source (Claude skill)2026-010 stars, merged into PuranOSsame shape (a skill), but nobody knows about it. The author puran-water's autocad-mcp has 660 stars, which shows the people building this have the technical skill; what they lack is an industry audience.
deepkick/pid2graph-vlm-eval, nurullaomar/pid-vlm-benchmarkOpen source20260–3 starevaluation demos that extract graphs with Claude or a VLM, not packaged as tools
YOLO-style symbol detection libraries (such as Automated-PnID-Symbol-Detection, 59 stars)Open sourceFrom ¥2022≤60 starrequires training a model and only does symbol detection; no loops or flow direction
just dropping the PDF into ChatGPT / ClaudeBig-company features—Everyonelarge sheets are unreadable; no tiling, no validation, no structured output. The Reddit complaints that "AI can't read P&IDs" come from exactly this.

Takeaway: the commercial side is already crowded, and the open-source side was there before it. No tool aimed at non-programmers that turns a PDF straight into a graph had passed 150 stars. This one has 300 stars now, more than pyDEXPI (271), making it the most-starred P&ID-focused repo on GitHub (sorting gh search for "P&ID" by stars puts it after the autocad-mcp group).

5. What's the differentiation, and is it why it broke out?

  • Technically, nothing here is unique. The path of "VLM reads the drawing + tiling + OCR validation + graph building" is also taken by Corvic, puran-water, and some academic demos. What's different is the packaging and the audience:
    1. Built for non-programmers. Download the ZIP, copy the folder, say one sentence to Claude. The README even explains how to show hidden folders on Windows and macOS.
    2. Works with scans. That's the real situation in older plants, and the commercial tools and the DEXPI route both skip it.
    3. Answers the reliability objection with QA reports and "flag what's unclear, don't guess". That lets engineers share it without fear of being called out by peers.
    4. Comes with public drawings you can try right away. The author curated a publicly licensed P&ID dataset with page references.
    5. Tells the story of "the context layer for AI troubleshooting". It isn't "drawing digitization", and it fits the author's wider body of work (fault-diagnosis agent, historian simulation, RCA benchmark).
  • Was it just the right moment? Half of it. These points made the post worth sharing among engineers, but the direct cause was the author's audience in LinkedIn's chemical and manufacturing circles, plus timing: frontier models had just become good enough at reading drawings, Claude Skills was hot, and the field was arguing over whether "LLMs can read P&IDs". puran-water built a skill of the same shape 10 months earlier and got 0 stars. That's the counterexample: the same thing without an industry audience doesn't take off.

6. Visibility and copycats

  • Visibility: circulating within a small circle. It went big in LinkedIn engineering circles (9k reactions), and industry newsletters and non-English accounts are reposting it. But HN, mainstream tech media, and the big AI accounts on X haven't covered it; x-radar has 0 hits. The project doesn't make money, so there is no public revenue.
  • Copycats:
    • Corvic AI promoted a similar hosted version, "P&ID Graph Studio", in the comments (it was already building this, and piggybacked on the post).
    • 11-17 someone opened a PR to port this skill to Hermes Agent / OpenCode (joelsansana).
    • Skills directories and non-English accounts are reposting it. No independent clone repos have been spotted yet.

7. What others can borrow

  • The playbook "vertical-industry practitioner + open-source Claude skill + long LinkedIn post" is replicable. The key is that the author already has an audience in that circle and real industry experience, not the code.
  • The post structure can be copied: an in-group argument → a concrete plant example → a direct answer to "AI can't" → admitting human review is needed → link in the comments → a public dataset to try right away.
  • On the product side: write install instructions for non-programmers; answer the "AI is unreliable" objection with QA reports and uncertainty flags; don't put sample results in the repo, so users have to test it on their own real drawings.
  • The same method transfers to other engineering drawing types: electrical single-line diagrams, HVAC, plumbing, PLC ladder logic, structural drawings. Open-source coverage of these is also nearly empty, but each needs someone from that industry to launch it.

8. Still unclear

  • Actual installs and usage are unknown: Download ZIP isn't counted, and stars and forks are only lower bounds.
  • The author's LinkedIn follower count (the page has a login wall, so I couldn't read it), so I can't calculate how far this post reaches relative to his audience.
  • Chart-reading accuracy: no public benchmark. Commenters from the field say "equipment and instrument matching is error-prone." The author's repo has a gold-set scoring script, but no scores are published.
  • Whether the author later turns it into consulting or a product (the site already has course and content entry points), and whether hosted versions like Corvic will take users away.
  • Whether there are Reddit posts or threads about it could not be verified (anti-scraping).

This article was written by AI from public data and the data we collect daily. Numbers are sourced, and inferences are labeled.