Skip to content

btmoriarty/kochab / skills/opportunity-brief

opportunity-brief

Verified

Research a company and a specific role, then produce an honest brief on whether it is worth pursuing. Use this whenever the user mentions a recruiter reaching out, a job posting they found, a company someone told them about, or a role they are weighing. Triggers on "a recruiter contacted me," "should I apply to," "what do you know about [company]," "look into this company," "is this role real," "assess this posting," "vet this opportunity," "a friend mentioned a job at," or when the user pastes a job description, recruiter email, or LinkedIn InMail. Also triggers on "compare these two roles" and "what should I ask the recruiter."

FileKindSize
SKILL.mdskill md8.4 KB
references/brief_template.mdmarkdown3.0 KB
references/fit_rubric.mdmarkdown2.5 KB
references/research_checklist.mdmarkdown3.6 KB

references/research_checklist.md

View on GitHub
# Research Checklist

Work top to bottom. Mark every item **[confirmed]** with a source, or **[inferred]**, or **[not found]**. Never silently upgrade an inference to a fact.

## 1. Identity and disambiguation (do this first)

- [ ] Exact legal name and primary domain
- [ ] Headquarters city and any office the role would sit in
- [ ] Founding year, headcount, and stage
- [ ] **Are there other organizations with this name?** Search the name plus an unrelated industry term. If a same-name entity exists, state the distinction explicitly in the brief and confirm which one the posting belongs to.

A brief built about the wrong company is worse than no brief. This step is not optional.

## 2. Money

- [ ] Public, private, nonprofit, PE-owned, or a project of a larger fiscal sponsor
- [ ] For companies: last funding round, amount, date, stage, lead investor. Total raised.
- [ ] For public companies: recent earnings direction, any restructuring announcements
- [ ] For nonprofits: primary funders, fiscal sponsor, whether the role is grant-funded and for what term
- [ ] Revenue or burn signals if visible. Is this org buying or cutting?

A two-year grant is a two-year job. Say so.

## 3. Stability, last twelve months

- [ ] Layoffs, hiring freezes, or a reduction in force
- [ ] Founder or C-suite departures
- [ ] Down round, bridge round, or a raise that looks like a rescue
- [ ] Lawsuits, regulatory action, or a public incident
- [ ] Acquisition, merger, or rumors of one
- [ ] Is this req a backfill, a new seat, or a repost? Check how long it has been listed.

## 4. Credibility

- [ ] Board and advisory board. Who lends their name to this?
- [ ] Investors or funders. Are they serious in this space?
- [ ] Named partners, customers, or venues where the work appears
- [ ] For young organizations, the advisor and funder list often carries more signal than the product

## 5. What the work actually is

- [ ] What the organization says it does
- [ ] What it visibly ships, publishes, or delivers
- [ ] The gap between those two, if any
- [ ] Which team the role sits on, and what that team owns

## 6. Employer reputation

- [ ] Glassdoor, Blind, Levels.fyi, read skeptically
- [ ] Look for **repeated, specific** complaints (a named manager, a pattern of unpaid overtime, a reorg every eight months). Ignore star averages and one-off rants.
- [ ] Tenure patterns on LinkedIn. If everyone on the team has been there under eighteen months, that is the finding.

## 7. The role itself

- [ ] Full posting text, not the title
- [ ] Years of experience asked, reporting line, comp band
- [ ] Location: real base, or pay-band disclosure? Days on-site? Travel?
- [ ] Requirements that are real filters vs. wish-list padding
- [ ] Buried conditions: on-call, weekend coverage, relocation, clearance, certification
- [ ] Comp band width. A band spanning more than about 60 percent usually means the level is undecided.

## 8. If a recruiter surfaced it

- [ ] In-house or agency?
- [ ] Did they name a specific req, a hiring manager, a comp band, and a process?
- [ ] Does the described role match any live posting on the company's own board?
- [ ] If none of the above, this may be pipeline-building rather than a live search. Say so.

## Sources worth checking

Company careers page and its Greenhouse, Lever, Ashby, or Workday board. LinkedIn (company page, people, job posting). Crunchbase or PitchBook for funding. News search for the last twelve months. SEC filings for public companies. ProPublica Nonprofit Explorer or Form 990 for nonprofits. Glassdoor and Blind for employee signal. The org's own blog, publications, or GitHub for what it actually ships.
add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks.Stars: 115kUpdated Claude CodeCodexVerifiedInstall