Uday Kang

Corpus Hub contributor since 2026-10-20

Uday Kang's work was selected for the XERJ Corpus Hub, the open reference memory AI coding agents search before they write code. When an agent meets the same problem, it gets this implementation back as a worked example, with the author and the repository attached.

1corpus

1selected commit

31files

2,215lines

★ 1GitHub stars on repo

Totals across every corpus @automatewithuday appears in; a commit selected for two corpora counts once. Files and lines count the selected commits; each corpus indexes the whole repository at its pinned commit.

What an agent can do with the linkedin-competitor-icp-scorer corpus

automatewithuday/linkedin-competitor-icp-scorer: Qualify the people engaging with your competitors' LinkedIn posts against your ICP: company fit first, then the buyer, every decision with…

Look up how linkedin-competitor-icp-scorer implements apify, claude, gtm, with answers cited to file and line.
Reuse a worked example: the commit “Redesign around guided ICP calibration and company-first qualification” (31 files · Python).
Answer from linkedin-competitor-icp-scorer's real Python source instead of memory (Databases and storage engines).

Example questions

Where does linkedin-competitor-icp-scorer handle “Redesign around guided ICP calibration and company-first qualification”?
How does linkedin-competitor-icp-scorer implement apify?
What does src do in linkedin-competitor-icp-scorer?

Paste it into your AI agent. It clones the repo at the pinned commit and indexes it on your machine.

Search the GitHub repository automatewithuday/linkedin-competitor-icp-scorer with XERJ (https://hub.xerj.org/corpus/automatewithuday--linkedin-competitor-icp-scorer).
Run these in a shell, in order, and check each result before the next:
1. xerj --help  (success: it prints usage). If xerj is missing: curl -fsSL https://xerj.org/get | sh
2. git clone https://github.com/automatewithuday/linkedin-competitor-icp-scorer linkedin-competitor-icp-scorer && git -C linkedin-competitor-icp-scorer checkout f859d56cf9ed65a1ce293d69aebda1c43977c983
3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data
4. xerj autoindex ./linkedin-competitor-icp-scorer --url http://127.0.0.1:9200 --prefix linkedin-competitor-icp --progress plain
5. xerj autoindex map --url http://127.0.0.1:9200
Then answer my question from the indexed files and cite the ax_path of every hit. Query syntax: https://xerj.org/llms.txt
Licence: MIT. Keep the copyright notice and credit the authors.

corpus automatewithuday--linkedin-competitor-icp-scorer · Databases and storage engines
Related corpora: griptape, aiohttp, sickn33/tidal-mcp, aberson/skill-mesh
Case study: reference coding for agents

Selected work

GitHub ★ 1

automatewithuday/linkedin-competitor-icp-scorer

f859d56cf9 Redesign around guided ICP calibration and company-first qualification

selected commit: 31 files · 2,215 lines · Python · src, tests, the project root

The corpus is the whole repository at the pinned commit, not only the files of the selected commit.

selected · in licence reviewcorpus automatewithuday--linkedin-competitor-icp-scorerDBMITapifyclaudegtmicplead-generationlinkedin agreed 2026-10-20

Not installable yet: this corpus is not in the hub registry until its licence review passes, so xerj corpus add and xerj ask cannot fetch it. It becomes installable when this card says live in the hub.

[![XERJ Corpus Hub contributor](https://hub.xerj.org/contributors/automatewithuday/badge.svg)](https://hub.xerj.org/contributors/automatewithuday)

Included with the author's permission (email, 2026-10-20), under each repository's own licence, with attribution. Want it removed? Reply to the email or open an issue on xerj-org/xerj.