Skip to content

getaero-io/gtm-eng-skills / engineering/warm-intro-scoring

warm-intro-scoring

Verified

FileKindSize
.gitignoreother121 B
GUIDE.mdmarkdown4.7 KB
LICENSEother1.1 KB
README.mdmarkdown8.0 KB
SKILL.mdskill md327 B
TESTING.mdmarkdown8.9 KB
UPSTREAM.mdmarkdown1.3 KB
assets/company-research.play.tsscript1021 B
assets/customer-db.sqlother2.7 KB
assets/evaluation-example.jsonconfig4.6 KB
assets/example.jsonconfig6.9 KB
assets/portfolio-focus.weights.jsonconfig32 B
assets/review.htmlother7.4 KB
assets/tuning-example.jsonconfig1.2 KB
assets/tuning.htmlother30.1 KB
check_all.pyscript1.4 KB
package-manifest.jsonconfig9.8 KB
plays/README.mdmarkdown18.2 KB
plays/check-report.pyscript1.8 KB
plays/check_all.pyscript1.6 KB
plays/check_parity.pyscript6.0 KB
plays/collect.play.tsscript4.0 KB
plays/collection.tsscript1.9 KB
plays/core.tsscript44.2 KB
plays/evaluation-contract.mdmarkdown3.4 KB
plays/evaluation.tsscript13.8 KB
plays/features.play.tsscript4.7 KB
plays/features.tsscript22.6 KB
plays/generatedtemplate.tsscript38.1 KB
plays/guardrails.tsscript948 B
plays/legacy.tsscript9.7 KB
plays/merge-payloads.pyscript8.6 KB
plays/parity-driver.tsscript995 B
plays/parity-evaluation.pyscript8.5 KB
plays/parity-reports.pyscript2.3 KB
plays/prepare-inputs.pyscript6.5 KB
plays/quality.tsscript3.8 KB
plays/read-sources.play.tsscript3.4 KB
plays/report-cli.tsscript590 B
plays/report.play.tsscript2.9 KB
plays/report.tsscript3.1 KB
plays/reports.tsscript5.7 KB
plays/research.play.tsscript1.6 KB
plays/review-uncertainty.play.tsscript5.5 KB
plays/score.play.tsscript2.3 KB
plays/snapshots.play.tsscript4.2 KB
plays/strict-json.tsscript1.8 KB
plays/sync-template.pyscript849 B
plays/uncertainty.tsscript4.9 KB
plays/validation.play.tsscript3.6 KB
references/adversarial-review.mdmarkdown7.0 KB
references/batch-collection.mdmarkdown5.1 KB
references/company-network.mdmarkdown5.8 KB
references/competitive-review.mdmarkdown8.8 KB
references/evaluation.mdmarkdown8.5 KB
references/evaluator-validation.mdmarkdown3.4 KB
references/evaluator.mdmarkdown7.9 KB
references/external-data.mdmarkdown4.0 KB
references/factor-test-matrix.mdmarkdown4.6 KB
references/factors.mdmarkdown6.1 KB
references/intro-drafts.mdmarkdown1.6 KB
references/pipeline.mdmarkdown7.6 KB
references/readable-output.mdmarkdown5.4 KB
references/research-brief.mdmarkdown2.4 KB
references/sources.mdmarkdown7.5 KB
references/tuning.mdmarkdown14.6 KB
scripts/audit_history.pyscript5.1 KB
scripts/check.pyscript5.1 KB
scripts/compare_versions.pyscript1.9 KB
scripts/evaluate.pyscript22.5 KB
scripts/package-skill.pyscript1.9 KB
scripts/portfolio.pyscript3.7 KB
scripts/quality.pyscript5.3 KB
scripts/recipe-demo.tsscript2.6 KB
scripts/render.pyscript1.6 KB
scripts/score.pyscript9.6 KB
scripts/temporal.pyscript2.2 KB
scripts/test_ask_handoff.pyscript2.1 KB
scripts/test_audit_history.pyscript2.7 KB
scripts/test_handoff_evaluate.pyscript9.1 KB
scripts/test_portfolio.pyscript3.6 KB
scripts/test_quality.pyscript3.1 KB
scripts/test_temporal.pyscript1.3 KB
scripts/test_tuning.pyscript14.1 KB
scripts/test_tuning_browser.cjsscript7.7 KB
scripts/test_version_parity.pyscript1.0 KB
scripts/tuning.pyscript10.9 KB
tests/adversarial.test.tsscript8.2 KB
tests/browser_e2e.cjsscript1.9 KB
tests/cloud_e2e.pyscript6.9 KB
tests/e2e-fixture.jsonconfig3.6 KB
tests/feature_parity.pyscript2.4 KB
tests/features.test.tsscript8.3 KB
tests/test_prepare_inputs.pyscript8.6 KB
tests/uncertainty.test.tsscript2.5 KB
vendor-manifest.jsonconfig748 B

references/factors.md

View on GitHub
# Candidate matching factors and evidence policy

Research date: 2026-09-23. The last30days window was August 24–September 23. Current first-party descriptions support examining both edges and communication context; they do not validate numeric weights or prove causal uplift. Recent social evidence was sparse/promotional, Reddit coverage partial, and some retrieved items unrelated. Those items do not justify new coefficients. The [retained synthesis](research-brief.md) records coverage separately.

[Happenstance's August 28 guide](https://happenstance.ai/guides/warm-intro-tools) distinguishes observed relationship networks from inferred co-employment networks and ranks both links in an intro path. Its companion guide to requesting an introduction emphasizes connector willingness, a specific target and a forwardable reason. These are vendor descriptions, not independent validation.

[Affinity's API documentation](https://api-docs.affinity.co/#relationship-strengths) describes relationship estimates from emails, calls and meetings and explicitly notes that these do not tell the whole story. Its [product description](https://www.affinity.co/product/relationship-intelligence) identifies recency and frequency. These are evergreen sources checked this run, not claims of a change within 30 days.

## Broad factor inventory

| Factor family | Evidence to collect | Treatment and failure mode |
|---|---|---|
| Actual introduction / collaboration | Dated intro completed, project/team records, connector confirmation | Strong evidence; a draft ask is not a completed intro. Never use future outcomes in retrospective features. |
| Both directed relationships | Owner→connector and connector→target evidence separately | An unknown edge holds the path; profile confidence cannot substitute for either edge. |
| Recency, frequency, duration | Dated interactions, distinct periods, relationship tenure | Candidate tie-break features; no arbitrary universal half-life. Old close colleagues can retain useful ties. |
| Reciprocity and channel | Replies in both directions, attended small meetings, calls, coauthorship | One-way sequences, newsletter opens, meeting invitations and bulk CCs are not reciprocal relationships. |
| Willingness and capacity | Explicit current yes/no, outstanding intro requests, connector cooldown | A decline blocks; unknown holds. Load-balancing is an operational constraint, not lower human worth. |
| Work overlap | Same canonical employer, real intersecting dates, duration | Candidate familiarity; verify team/location/reporting context, especially at a large employer. |
| Shared team / manager / project | Source-supported team identity and intersecting tenure | Potential improvement over company overlap; never infer from job title alone. |
| Previous roles and function | Normalized duties, adjacent functions, shared problems | Stronger room-match relevance than intro proof. Different titles may describe similar work. |
| Career stage and company type | Scope/seniority, operator/founder stage, B2B/B2C, startup/enterprise | Context-specific affinity or complementarity; no age inference. |
| Industry, vertical, niche | Explicit customer sector and projects, sourced professional posts | Prefer task-specific relevance over generic title similarity. Separate product fit. |
| School, cohort, course, lab | Canonical school, dated cohort, shared lab/project | Broad alumni overlap is weak; actual shared small-group activity is stronger context. No prestige weighting. |
| Clubs, co-ops, college sports | Public/self-declared non-sensitive activity and overlap | Conversation context only; exclude affiliations revealing protected/sensitive traits. No inference from name, appearance or fraternity label. |
| Hometown, location, language | Voluntary professional context, relevant time/location overlap | Optional context, not origin/ethnicity proxy or automatic warmth. Countries worked in remain excluded from the event baseline. |
| Public social interaction | Verified account identity, reciprocal specific replies/co-creation | Likes, follows, mentions and popularity are weak; do not infer personality or private relationships. |
| Common interests | Explicit professional interests, activities people choose to share | Useful event icebreakers; do not mine private life or infer sensitive traits. |
| Network structure | Verified mutual edges, independent supporting sources, hop count | Duplicate sources do not add evidence; celebrity degree/popularity does not imply access. Each extra hop needs proof. |
| Investor, board, advisor, partner | Named individual role and actual relationship, not just portfolio overlap | Investor context capped; portfolio adjacency cannot carry a warm route alone. |
| Reason to meet / complementarity | Requester's specific ask, target remit, shared or complementary goal | Rank task fit separately; identical backgrounds are not always the best match. |
| Availability and eligibility | Current roles, conflicts, opt-in, suppression, already-introduced status | Gates outside factual similarity. Do not equate Going with arrival or arrival with consent. |
| Provenance and uncertainty | Identity resolution, date precision, contradictions, source age, coverage | Show missingness; avoid penalizing sparse profiles as if evidence disproved a tie. |

## What changes now

Preserve deterministic baseline weights and source priority. The implemented improvement is a conservative review gate requiring evidence on both edges and specific willingness; it changes draft eligibility, not numerical fit. The artifact displays the separate fields. Recency/reciprocity, team-level overlap, relevance, capacity and complementary goals remain candidate extensions until sufficient point-in-time labels exist. No honest study can establish that “all potential factors” improve matching merely by listing them.

Test one feature family at a time, use ablation against the fixed baseline, and measure performance on the same held-out candidate set. Evaluate subgroup coverage by job function/company size/profile completeness to detect systematic missing-data artifacts without inferring protected traits.
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall