agentleFS
Sign inStart free
askoulwassimaskoulwassim/perfect-placement/skills/research/SKILL.md

research

Skill3 starsChanged 34 days agoMITView on GitHub

Build or refresh a company dossier for a picked role (mission, products, stage, funding, leadership, news, culture, risks, remote and comp reality, authentic hooks, interview themes) and save it with the `companies.dossier.write` op. Reuses an existing dossier unless a refresh is asked for or an interview is near. Starting it picks an active or held role (on-deck).

189 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use daily-arxiv, exp-eval and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • LambenthanSkill

    daily-arxiv

    每日从 arXiv 拉取新论文，过滤相关性，auto-ingest 高优先级论文，检测 SOTA 更新

    Also in 5 projects that use this

  • LambenthanSkill

    exp-eval

    实验判决门：Review LLM 独立评判实验结果 → 4 种判决路径 → 自动更新 claims confidence、ideas status、graph edges

    Also in 5 projects that use this

  • truongtv22Skill

    Problem-Solving Techniques

    Apply systematic problem-solving techniques for complexity spirals (simplification cascades), innovation blocks (collision-zone thinking), recurring patterns (meta-pattern recognition), assumption constraints (inversion exercise), scale uncertainty (scale game), and dispatch when stuck. Techniques derived from Microsoft Amplifier project patterns adapted for immediate application.

    Also in 5 projects that use this

  • liufeng1976Skill

    setup-ts-deep-modules

    Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.

    Also in 43 projects that use this

  • skyllwtSkill

    exp-pilot-eval

    Pilot result evaluation — read pilot results, apply success criteria, update idea page (pilot_result, failure_reason if failed), generate PILOT_VERDICT_REPORT. Called by /ideate Phase 5 after /exp-pilot-run.

    Also in 4 projects that use this

  • skyllwtSkill

    exp-pilot-run

    Pilot experiment execution — read Pilot Spec YAML, write pilot code, run experiment(Confirm with the user before operation and require the applicant to conduct manual inspection), return results. Called by /ideate Phase 5. Does NOT modify wiki pages or judge pass/fail.

    Also in 4 projects that use this

  • +5 more from Lambenthan
  • +1 more from skyllwt

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 169 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never fabricate funding, news or people.

    line 42
  2. Distinctive:

    Every write is an op. Never submit an application or send an email.

    line 44

“Common” is measured: kept by at least 6 in 10 of the 169 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.

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

Research

A crisp, current, sourced dossier that feeds tailoring, outreach and interview prep. One dossier per company, shared by all of its roles.

When

On pick (starting Research, Tailor or Connect moves an active or held role to on-deck, "In progress", #105), before tailoring, or before an interview (refresh time-sensitive facts only).

Skip check (first)

roles.get { role_id } returns the company. If company.md_path is set, a dossier exists: reuse it. Only write when there is none, the user asks for a refresh, or an interview is scheduled (then refresh funding, news, leadership).

Steps

  1. runs.start { skill: "research", role_id }.
  2. Research (web search and fetch; cite and date every time-sensitive fact):
    1. Basics: what they do, products, founding, HQ, size.
    2. Current: latest funding and investors, news from the last 6 to 12 months, leadership and the hiring team, trajectory.
    3. Stage and a legitimacy verdict for unknown companies: go, caution or avoid.
    4. Remote and comp reality against the Work mode and Terms components.
    5. Culture and how they interview.
    6. Authentic fit hooks mapped to the Story component (for the cover letter and outreach).
    7. Interview themes and 3 to 5 sharp questions to ask.
  3. companies.dossier.write { company_id, markdown, role_id }. The op writes companies/<slug>/dossier.md, sets the company's md_path and links the dossier into every open application at that company.
  4. runs.finish { run_id, status: "ok" }.

Tools

A headless run pre-approves exactly these (SKILL_GRANTS in packages/engine/runners/grants.ts; a test keeps this list and that one equal) and denies everything else. If one you need is denied or missing, do not work around it: runs.finish { run_id, status: "error", summary: { error: "tool denied: <tool>", denied_tools: [...] } }.

  • {{tool:pp}}: the pp MCP tools (every Perfect Placement read and write is an op).
  • {{tool:web.search}}: find sources for the dossier.
  • {{tool:web.fetch}}: read each source.

Rules

  • Never fabricate funding, news or people. Flag anything stale or unverifiable.
  • The dossier never changes a role's status beyond the pick: runs.start (or companies.dossier.write with role_id) moves an active or held role to on-deck; later statuses are never touched.
  • Every write is an op. Never submit an application or send an email.

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.

Check your setup, free