Skip to main content
skill CX Codex

company-intel · nishant-tiwari24 — Claude Code skill: what it does, how to install

company-intel — a skill for Claude Code and Codex that generates interview preparation briefs for target employers. Runs when naming a company before technical or behavioral rounds.

MIT ★ 345 updated 2026-11-14

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add nishant-Tiwari24/cracked
/plugin install cracked@cracked
Open on GitHub

What company-intel does

The skill compiles company-specific hiring briefs covering online assessment formats, interview stages, and reported LeetCode problems. If a cached brief exists in $CRACKED_DIR/companies/ and is under 30 days old, it reuses the file directly.

Execution relies on a bundled scripts/questions.py tool that queries a community dataset of over 470 companies with custom time windows like 30 days, 3 months, or 6 months. When web search is available, it retrieves official company principles and recent interview experiences, falling back to ARCHETYPES.md when offline.

The tool requires python3 to execute the question fetcher, and GitHub API rate limits on shared networks require setting GITHUB_TOKEN.

What it helps with

  • fetch company-specific LeetCode problems filtered by topic and time
  • outline online assessment formats and interview stage sequences
  • extract company principles for behavioral interview rounds
  • cache employer hiring bars for mock interviews and resume checks

Example prompts for the agent

  • I have a Google interview next week, build a prep brief
  • What questions and topics are most frequent in Amazon OA?
  • Prep me for Flipkart technical rounds

How to install company-intel

1Plugin marketplace

/plugin marketplace add nishant-Tiwari24/cracked
/plugin install cracked@cracked

This installs the whole cracked plugin with all its skills

2Skills CLI (Vercel)

npx skills add nishant-Tiwari24/cracked --skill company-intel -a claude-code

3Manually: put the files in place

~/.claude/skills/company-intel/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/company-intel/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about company-intel

How to install company-intel in Claude Code?

Run /plugin marketplace add nishant-Tiwari24/cracked and then run /plugin install cracked@cracked.

What does company-intel do?

It generates and caches a targeted brief covering an employer's hiring stages, assessment details, values, and frequent interview problems.

What is required to run company-intel?

A local python3 runtime is required for questions.py. A GITHUB_TOKEN environment variable is needed if requests hit GitHub API rate limits.

Source text

SKILL.md · MIT
---
name: company-intel
description: Build or load a cached prep brief for a specific target company covering its interview process and rounds, OA format, the LeetCode questions and topics most frequently reported for it (recent and all-time), what its resume screen values, its stated values or leadership principles, and system design and HR focus. Every cracked skill uses this when the candidate names a company. Use when the user says they're preparing for a specific company ("I have a Google interview", "prep me for Amazon", "Flipkart OA next week"), asks what a company asks, or wants company-wise questions.
---

# Company intel

When a candidate names a company, every cracked skill gets sharper: the OA uses that company's reported questions, the HR round asks about its values, and the resume roast checks against its bar. This skill builds that knowledge **once**, caches it, and hands it to whichever skill asked.

**No company named? Don't ask.** Skills work fine without one: a generic product-company style is the default. Only build a brief when the user names a company or the profile's `target_companies` lists one and the calling skill wants it.

## 0. Load or build

1. Call the Skill tool with "cracked-profile".
2. Normalise the company name (e.g. "goog" → "Google"), then read `$CRACKED_DIR/companies/<company-slug>.md`.
   - If it exists and its `updated:` date is under 30 days old, use it. Say one line ("Loaded Google brief, updated 2026-10-30") and hand back.
   - If it's older, or missing, build it (below). If the calling skill only needs questions, you can do just §1.

## 1. Reported questions (always, if online)

Run the bundled script. It fetches the community-maintained company-wise LeetCode dataset ([liquidslr/leetcode-company-wise-problems](https://github.com/liquidslr/leetcode-company-wise-problems), 470+ companies, frequency-ranked) and caches it in `$CRACKED_DIR/cache/`. Every output ends with a freshness line (`cached <date> · dataset last updated upstream <date>`): quote it, and if the upstream date is more than ~3 months old, tell the user the data may be stale.

```bash
python3 <this-skill-dir>/scripts/questions.py list <query>                 # find the exact company name
python3 <this-skill-dir>/scripts/questions.py topics "<Company>"            # topic + difficulty mix (last 6 months)
python3 <this-skill-dir>/scripts/questions.py get "<Company>" --window 3m --limit 30
python3 <this-skill-dir>/scripts/questions.py get "<Company>" --difficulty medium,hard --topic graph
```

`<this-skill-dir>` is this skill's base directory (most harnesses print it when the skill loads). If you can't see it, locate the script with:
`find ~/.claude ~/.codex ~/.agents ~/.cursor ~/.gemini ~/.config "$PWD" -path '*company-intel/scripts/questions.py' 2>/dev/null | head -1`.
Other skills that need questions use the same script path. Tell them the absolute path when you hand back.

Windows: `30d`, `3m`, `6m` (default), `older`, `all`. Use `--format json` when another skill needs to pick problems programmatically.

- Names match case- and punctuation-insensitively, with aliases for common long forms ("Tata Consultancy Services" → `tcs`, "Facebook" → Meta, "AWS" → Amazon). If there's still no match, it suggests close names: confirm with the user.
- An empty window widens automatically (30d → 3m → 6m → all) and prints `window widened from X to Y`. Say which window you actually used.
- If you hit GitHub's rate limit on a shared network, set `GITHUB_TOKEN`.
- If the company isn't in the dataset (common for small startups, and for some service companies), say so, then fall back to the closest archetype in [ARCHETYPES.md](ARCHETYPES.md).
- If you're offline, use the cache. If there's no cache, use the archetype and say so.
- **Provenance**: always label these as "frequently reported by candidates (community dataset)", never as the company's official or leaked question bank.

## 2. Process, values and resume bar (web, if available)

If you have a web search or fetch tool, research these from **public** sources, and keep each source's URL:
- The official careers page and "how we hire" or interview-prep pages. Many large companies publish them.
- Public interview experiences: LeetCode Discuss (company tag), GeeksforGeeks interview experiences, Glassdoor interview reviews, Reddit (r/cscareerquestions, r/developersIndia), and company engineering blogs.
- The company's published values or leadership principles (for example, Amazon publishes its Leadership Principles).

Extract: the round sequence (OA → technical × N → system design → HR or hiring manager), OA platform, duration and question count, interview language rules, what's emphasised, recent changes (dated), and the role and level the experiences refer to. Prefer the last 12 months. Note conflicts between sources rather than picking one silently.

**If you have no web tool**: say so, fill §2 from the archetype, and mark it `unverified: no web access`. Never present general knowledge as current fact. Hiring processes change.

## 3. Write the brief

Save `$CRACKED_DIR/companies/<company-slug>.md` in this shape. Keep it under ~120 lines, since other skills read it:

```markdown
# <Company> prep brief
updated: <YYYY-MM-DD> · role focus: <e.g. SDE-1 / new grad> · archetype: <from ARCHETYPES.md>

## Process (reported)
1. <round> · <format> · <duration> · <what's assessed>
…
Sources: <urls>

## OA
<platform, count, difficulty mix, time, language rules, typical topics>

## DSA focus (community dataset, window: <w>)
Difficulty mix: …
Top topics: …
Top 15 recent questions: | Difficulty | Title | Topics | Link |

## System design
<expected at this level? HLD or LLD? typical prompts reported>

## Values / behavioral
<published values or principles, and the behavioral themes interviewers probe>

## Resume screen
<what this company's screen is reported or known to value; must-have keywords for the role>

## Gotchas
<e.g. "bar raiser round", "no IDE, shared doc only", "CGPA cutoff reported for campus drives">
```

## 4. Hand back

Give the calling skill (and the user) a 3–5 line summary: process, top 5 topics, the OA shape, and one gotcha. Then continue with the calling skill. If the user invoked this directly, offer next steps: `/oa-sim <company>`, `/mock-interview <company>`, `/resume-blueprint <company>`, `/hr-round <company>`.

---

*Skill calls:* if your agent has no Skill tool, open the named skill's `SKILL.md` in the cracked skills folder (`core/`, `interview/`, `profile/`, `strategy/`) and follow it instead.

© Nishant Tiwari · MIT · nishant-Tiwari24/cracked

Similar skills

All skills for Agent setup: memory, context, orchestration →

company-intel by other authors comes first.

From the same set20

The whole set →
offer-decode The offer-decode Claude Code skill breaks down a job offer and estimates take-home pay. It runs on an offer letter, a CTC breakdown, or a request to compare terms and draft a negotiation reply. CX Codex +1 ★ 345repo stars system-design-mock The system-design-mock Claude Code skill runs practice interviews for system design, from fresher to SDE-2 level. It starts when someone asks to rehearse HLD or LLD, including a design prompt for a specific system. CX Codex +1 ★ 345repo stars referral-dm The referral-dm Claude Code skill drafts tailored messages for referral requests and job outreach. It can respond to hiring posts, contact recruiters or alumni, and write follow-ups. CX Codex +1 ★ 345repo stars github-glowup The github-glowup Claude Code skill audits a GitHub profile from a recruiter’s perspective and drafts improvements. Run it to revise a profile, select pinned repositories, or write a profile README. CX Codex +1 ★ 345repo stars roast-my-resume roast-my-resume — a Claude Code skill that reviews technical resumes and suggests edits. It checks ATS readiness, recruiter-facing presentation and weak bullets against the candidate’s experience and target company. CX Codex +1 ★ 345repo stars defend-my-project The defend-my-project Claude Code skill prepares candidates to discuss their own projects in interviews. It examines a repository, asks code-specific questions and builds a sheet of prepared answers. CX Codex +1 ★ 345repo stars oa-sim The oa-sim Claude Code skill builds a practice online assessment and grades code against hidden tests. It starts when someone asks for an OA, coding-round practice, or a company placement test. CX Codex +1 ★ 345repo stars cracked-profile The cracked-profile Claude Code skill keeps a candidate profile and a record of interview-prep progress. It runs to create or edit that profile, review past scorecards, or provide profile data to another cracked skill. CX Codex +1 ★ 345repo stars

Project sponsors

Companies that keep this analytics open