agentleFS
SirjanSinghSirjanSingh/oahelper-mcp/skills/oa-compare/SKILL.md

oa-compare

Skill2 starsChanged 27 days agoMITView on GitHub

Compare the online-assessment patterns of several companies from OAHelper (question count, coding vs MCQ split, difficulty, topics, recency) to decide what to study first or which OAs overlap. Use when the user says "compare X and Y OAs", "which of these companies' OAs are similar", "what topics are common across my upcoming OAs", or lists several companies they are applying to.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    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
  1. Very specific:

    If not saved, oahelper_search(company) (one request) gives set dates, counts and question types.

    line 14
  2. Distinctive:

    Ask before syncing more than 4 companies in one go.

    line 18
  3. Distinctive:

    Use sets from the last 12 months.

    line 22

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Compare OAs across companies

Part of oahelper-mcp by Sirjan Singh.

1. Gather (cheap first)

For each company:

  1. oahelper_offline(company). Use the saved pack when it exists.
  2. If not saved, oahelper_search(company) (one request) gives set dates, counts and question types. That is enough for the comparison table. Only run oahelper_sync if the user wants topic-level detail, and cap it at about 20 requests per company.

Ask before syncing more than 4 companies in one go; it burns the daily cap.

2. Compare

Use sets from the last 12 months; fall back to older ones and flag it.

ColumnFrom
Sets in last 12 monthsset dates
Questions per OAset question counts
Coding / MCQ / SQL splitquestion types
Typical difficultydifficulty scores of saved questions
Top topicsquestion titles, tags and statements
Latest setnewest date

3. Output

  1. The table above, one row per company.
  2. Shared topics: topics that appear in 2 or more companies, ranked by how many. These are the highest-leverage things to study.
  3. Company-specific: anything only one company tests (e.g. SQL only at X).
  4. Study order: a short ranked list, factoring in the OA dates if the user gave them.

Say where data is thin (one set, old sets, no saved questions). Write UNKNOWN instead of guessing a number.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.