Token导航 LogoToken导航TokenDH.com
研究检索权限需确认github未标认证来源可访问许可证需确认审计提醒

portfolio-deal-linker投资组合交易链接器

Agent Skill

portfolio-deal-linker 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

392

周安装

16

GitHub Stars

12

下载量

125
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:portfolio-deal-linker(投资组合交易链接器)
来源仓库:https://github.com/scientiacapital/skills
仓库路径:skills/portfolio-deal-linker
安装命令:
npx skills add https://github.com/scientiacapital/skills --skill portfolio-deal-linker
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/scientiacapital/skills --skill portfolio-deal-linker

简介

用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中快速定位候选结果。

  • 可结合关键词、任务场景或来源线索进行信息筛选。
  • 通过 npx skills add 命令从指定 GitHub 仓库安装使用。
  • 建议确认权限范围和维护状态,避免触发联网或文件读写操作。
  • portfolio-deal-linker 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

<quick_start> Daily automated run (7am CST): Checks for deals closed since last run → attributes to skills/actions → updates portfolio

On-demand: "portfolio update" → runs full attribution scan now "what did I influence this month" → generates monthly impact report "gtme evidence" → formats portfolio for interview/review context

Trigger phrases:

  • "portfolio update" / "deal closed"
  • "link deal to portfolio" / "gtme evidence"
  • "what did I influence" / "career evidence"
  • "transition tracker" / "show my impact" </quick_start>

<success_criteria>

  • Every closed-won deal attributed to originating skill/workflow within 24 hours
  • Revenue influenced tracked with clear attribution chain
  • Time-saved metrics aggregated weekly (skills that eliminated manual work)
  • Portfolio evidence formatted for VP BD transition narrative
  • Monthly executive summary auto-generated
  • Zero missed attributions on deals Tim touched </success_criteria>

Architecture

SCHEDULED (7am CST)           ATTRIBUTION                 PORTFOLIO UPDATE
──────────────────────────────────────────────────────────────────────────────
HubSpot: recently closed  →  Match deal to skill that  →  Update portfolio.jsonl
deals (won + lost)        →  originated/influenced it  →  Update weekly digest
                          →  Calculate metrics         →  Update GTME narrative
                          →  Compare to manual baseline →  Career evidence file

Stage 1: Detect Newly Closed Deals

Use hubspot_search_deals with filters:

  • dealstage IN ('closedwon', 'closedlost')
  • closedate >= last run timestamp (stored in ~/.claude/portfolio/last-run.json)
  • Exclude channel deals (is_channel = true) and owned by AE IDs '82625923', '423155215', '190030668' (Lex Evans, Ron Epstein, Phillip Sandler)

For each deal, pull:

FieldPurpose
dealnameIdentification
amountRevenue attribution
closedateCycle time calculation
createdatePipeline velocity
dealstageWon vs lost
hubspot_owner_idTim's deals only
Associated contactsWho was engaged
Associated companyCompany match
Deal notes/activityAttribution signals

Stage 2: Skill Attribution Engine

For each closed deal, determine which skills/automations contributed:

Attribution Signals

SignalSkill AttributedHow to Detect
Contact was loaded via Apollo sequenceprospect-research-to-cadenceApollo emailer_campaigns_search — check if contact was in a sequence
MEDDIC call prep was generatedmeddic-call-prep-autoCheck if company appears in call prep logs
Deal was flagged by momentum analyzerdeal-momentum-analyzerCheck if deal appeared in RED/YELLOW actions
Contact enriched via Apolloprospect-research-to-cadenceApollo contact create date vs deal create date
Outreach email was draftedprospect-research-to-cadenceGmail draft history for contact email
Activity history existsmeddic-call-prep-autoask_agent — query activity timeline for company
Manual prospecting (no automation match)Tim (manual)Fallback — still counts for portfolio

Attribution Model

PRIMARY attribution (100% credit):
  → Skill that ORIGINATED the deal (first touch)

ASSIST attribution (shared credit):
  → Skills that INFLUENCED the deal (middle touches)
  → E.g., prospect-research found the contact, meddic-call-prep prepped the demo,
    deal-momentum flagged it when stalling

RECOVERY attribution:
  → If deal-momentum-analyzer flagged deal as RED/YELLOW
    AND deal subsequently closed-won
  → This is "recovered revenue" — strongest GTME evidence

Stage 3: Calculate Portfolio Metrics

Per-Deal Metrics

MetricFormulaWhy It Matters
Cycle timeclosedate - createdatePipeline velocity
RevenueamountDirect impact
Cost to closeEstimated from skill usage costsEfficiency
Automation touchesCount of skill attributionsLeverage
Manual vs automated% of deal lifecycle automatedTransition evidence

Aggregate Metrics (Rolling 30 days)

MetricFormulaTarget
Total revenue influencedSum of attributed closed-won dealsTrack monthly
Deals recoveredDeals flagged RED/YELLOW → closed-won5-10% of pipeline
Time saved (hours/month)Sum of skill time-saved estimates × usage count30+ hrs/mo
Cost per dealTotal automation cost / deals closed< $5/deal
Automation coverageDeals with ≥1 skill touch / total deals> 80%
Win rate liftAutomated deal win rate vs manual baselineTrack delta

GTME Positioning Metrics

MetricNarrativeVP BD Relevance
Revenue influenced/month"I influenced $X in pipeline through automated workflows"Revenue ownership
Hours saved/month"Built systems that save 30+ hours/month of manual work"Operational leverage
Cost per lead"Reduced cost-per-qualified-lead from $X to $Y"Unit economics
Recovery rate"Recovered $18K/month in stalled pipeline through automated detection"Pipeline management
Automation coverage"80%+ of deals now touch at least one automated workflow"Systems thinking

Stage 4: Update Portfolio Files

4a. Append to portfolio.jsonl

{
  "date": "2026-03-15",
  "deal_id": "hs_12345",
  "deal_name": "Baylor University",
  "amount": 45000,
  "outcome": "closedwon",
  "cycle_days": 32,
  "primary_skill": "prospect-research-to-cadence",
  "assist_skills": ["meddic-call-prep-auto", "deal-momentum-analyzer"],
  "recovered": true,
  "recovery_skill": "deal-momentum-analyzer",
  "automation_touches": 5,
  "manual_touches": 3,
  "automation_pct": 0.625
}

4b. Update Weekly Digest

Append deal to the existing portfolio-artifact weekly digest with attribution details.

4c. Generate Monthly GTME Evidence Report

╔══════════════════════════════════════════════════════════════╗
║  GTME PORTFOLIO — [Month Year]                               ║
║  Tim Kipper | BDR → VP Business Development                  ║
╠══════════════════════════════════════════════════════════════╣

HEADLINE METRICS:
┌─────────────────────────────────────────────────────────────┐
│ Revenue Influenced:  $[XXX,XXX]  (XX deals)                 │
│ Pipeline Recovered:  $[XX,XXX]   (X deals saved from stall) │
│ Time Saved:          [XX] hours  ([X] min/day × [XX] days)  │
│ Automation Coverage: [XX]%       (deals with skill touch)    │
│ Cost per Deal:       $[X.XX]     (automation cost / deals)   │
└─────────────────────────────────────────────────────────────┘

SKILL ATTRIBUTION BREAKDOWN:
| Skill | Deals Influenced | Revenue | Time Saved |
|-------|-----------------|---------|------------|
| prospect-research-to-cadence | XX | $XX,XXX | XX hrs |
| meddic-call-prep-auto | XX | $XX,XXX | XX hrs |
| deal-momentum-analyzer | XX (recovered) | $XX,XXX | XX hrs |

TOP DEALS (with attribution chain):
1. [Deal] — $XX,XXX | Won
   Chain: Apollo enrich → sequence load → call prep → demo → close
   Skills: PRC → MCA → DMA

VP BD TRANSITION NARRATIVE:
"In [Month], I influenced $[X] in revenue through automated GTM systems
I designed and built. These systems saved [X] hours of manual work,
recovered $[X] in stalled pipeline, and achieved [X]% automation
coverage across the deal lifecycle. This demonstrates [operational
leverage / systems thinking / revenue ownership] at VP BD scale."

╚══════════════════════════════════════════════════════════════╝

Stage 4: Comp Plan Attainment Tracker

Calculate daily progress against Tim's 2026 BDR comp plan targets.

March 2026 Targets (Ramp 50%)

MetricMonthly TargetStretch (126%+)Daily Run Rate
Deals created1216+0.6/day
Pipeline generated$357,000$450,000+$17,850/day
Revenue (closed-won)$125,000$157,000+$6,250/day

Calculation Logic

  1. Query HubSpot for deals created this month where Tim is owner (87486452) or collaborator
  2. Sum amount for pipeline generated
  3. Sum amount where dealstage = 'closedwon' for revenue
  4. Calculate:

- Pipeline attainment % = total pipeline / monthly target × 100 - Revenue attainment % = total closed-won / monthly target × 100 - Deal count attainment % = deals created / monthly target × 100 - Accelerator zone: <100% = base, 100-110% = 1.0x, 111-125% = 1.25x, 126%+ = 1.5x - Days remaining = business days left in month - Required daily run rate = (target - achieved) / days remaining

Output Format (append to daily portfolio report)

📊 COMP PLAN TRACKER — March 2026 (Ramp 50%)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Pipeline:  $XXX,XXX / $357,000  (XX% — Zone: BASE/1.0x/1.25x/1.5x)
Revenue:   $XX,XXX / $125,000   (XX% — Zone: BASE/1.0x/1.25x/1.5x)
Deals:     X / 12               (XX%)
Days left: X business days
Gap to stretch: $XXX,XXX pipeline | $XX,XXX revenue | X deals
Daily run rate needed: $X,XXX pipeline | $X,XXX revenue

Monthly Target Lookup (for future months)

MonthDealsPipelineRevenuePhase
March12$357K$125KRamp 50%
April16$464K$163KRamp 65%
May20$607K$212KRamp 85%
June24$714K$250KFull (H1)
July+24$714K$475-600KFull (H2)

Dynamically select targets based on current month.

<scheduled_automation>

Daily 7am CST Run

Schedule: Daily at 7:00 AM CST (13:00 UTC), weekdays Task name: "portfolio-deal-linker-daily" Flow:

  1. Check HubSpot for deals closed since last run
  2. Attribute each deal to originating skills
  3. Calculate per-deal and aggregate metrics
  4. Append to portfolio.jsonl
  5. Update weekly digest if new closed-wons
  6. Generate monthly report if month-end

Integration with EOD: When Tim says "EOD", include portfolio attribution summary for any deals closed today. </scheduled_automation>

Sibling Skills Referenced

  • portfolio-artifact-skill — Base metrics capture, weekly digest format, executive summary template
  • deal-momentum-analyzer-skill — Recovery attribution (deals flagged RED/YELLOW that closed-won)
  • prospect-research-to-cadence-skill — Origination attribution (Apollo sequence enrollment)
  • meddic-call-prep-auto-skill — Influence attribution (call prep generated for deal)
  • hubspot-revops-skill — HubSpot query patterns, deal stage definitions

Emit Outcome Sidecar

As the final step, write to ~/.claude/skill-analytics/last-outcome-portfolio-deal-linker.json:

{"ts":"[UTC ISO8601]","skill":"portfolio-deal-linker","version":"1.0.0","variant":"default",
 "status":"[success|partial|error]","runtime_ms":[estimated ms from start],
 "metrics":{"deals_linked":[n],"skills_attributed":[n],"revenue_tracked_usd":[n]},
 "error":null,"session_id":"[YYYY-MM-DD]"}

Use status "partial" if some stages failed but results were produced. Use "error" only if no output was generated.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

36.16%
按下载量换算45

Claude

28.41%
按下载量换算36

Cursor

18.48%
按下载量换算23

Gemini CLI

10.07%
按下载量换算13

安全审计

Gen Agent Trust Hub

通过

Socket

可疑

Snyk

通过

权限和风险

权限需确认

当前来源未能明确判断权限范围,默认进入异常复核队列。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills