Generated banner for AI Readiness
Generated logo for AI Readiness

AI Readiness

AnthropicOfficialPublished by Anthropic

  • Skill
  • Research and analysis
  • Business and productivity
  • Apache-2.0
  • No issues found

From the author

Scan the portfolio for the highest-leverage AI opportunities and rank where to deploy operating-partner time. Ingests quarterly updates and financials across multiple portfolio companies, identifies quick wins at each, and stacks them into a single ranked action list. Use during quarterly portfolio reviews, annual planning, or when deciding which companies get AI investment first. Triggers on "AI readiness", "AI opportunity scan", "where should we deploy AI", "AI across the portfolio", "AI quick wins", or "which portcos are ready for AI".
— the description by Anthropic

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a systematic approach for evaluating portfolio companies to determine where AI investments will yield the highest EBITDA impact. By ingesting financial and operational data, the agent performs a per-company scan to identify quick wins, ranks these opportunities based on financial impact and speed to value, and highlights cross-portfolio 'replays' to maximize efficiency. It is designed to help operating partners make data-driven decisions during quarterly reviews and annual planning cycles.

What it does

  • Ingests and analyzes quarterly updates, financials, and board materials from portfolio companies.
  • Evaluates potential AI projects against strict readiness gates including data quality, internal ownership, and pilot feasibility.
  • Ranks AI opportunities across the entire portfolio based on projected EBITDA contribution and speed to value.
  • Identifies repeatable playbooks that can be deployed across multiple companies to leverage shared learnings.
  • Generates a concise summary report for operating partners, including a ranked action list and clear Go/Wait status for each company.

When to use it

  • During quarterly portfolio reviews to determine where to focus operating-partner time.
  • When conducting annual planning to set AI investment priorities.
  • When deciding which portfolio companies are best positioned for immediate AI deployment.
  • When looking for cross-company synergies to scale successful AI implementations.

Advantages

  • Prioritizes high-impact financial outcomes over speculative technology trends.
  • Prevents wasted effort by identifying blockers early through rigorous gate checks.
  • Maximizes ROI by identifying repeatable 'replays' across similar portfolio companies.
  • Provides a clear, objective rationale for why certain projects are prioritized or deferred.

Usage examples

“AI readiness scan for the Q3 portfolio data.”
The agent processes the uploaded board packs and financials, returning a ranked table of the top 5 AI opportunities across the portfolio and a list of recommended cross-company replays.
“Which portcos are ready for AI?”
The agent evaluates the current portfolio data against the three readiness gates and provides a list of companies that are 'Go' for immediate pilots versus those that need to 'Wait' due to data or ownership gaps.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/anthropics/ai-readiness/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip ai-readiness.zip -d .agents/skills

Documentation by Anthropic

Portfolio AI Readiness

Workflow

Step 1: Connect to Portfolio Data

First, ask the user where the portfolio materials live. Don't assume — offer the options:

  • MCP servers — data room, SharePoint, Google Drive, or a portfolio-ops database if one is connected

  • Local files — a folder path on disk with quarterly decks, financials, board packs

  • File uploads — drag PDFs, PowerPoint, or Excel directly into the conversation

Once connected, pull quarterly updates, board decks, and financials for the portfolio (or a subset). For each company, extract: sector, revenue, headcount by function, tech stack mentioned, and any AI/automation initiatives already in flight.

If the user provides a single company, still run the scan but skip the cross-portfolio ranking.

Ask up front if not obvious from materials:

  • Hold period remaining per company (AI payback matters less 12 months from exit)

  • Whether any portco has already deployed something that worked

Step 2: Per-Company Scan

For each company, answer three gate questions. All three yes → Go. Any no → Wait with a note on what unblocks it.

  1. Is the data there? Can they produce a clean input for the use case — customer list, invoice feed, contract repository — without a 6-month data project first?

  2. Is there an owner? Someone on the management team who will drive this, not a sponsor who will "support" it.

  3. Can we pilot in 30 days? One team, one workflow, off-the-shelf tooling. If the answer starts with "first we'd need to...", it's not a quick win.

Then identify the top 2-3 leverage points. Look for these patterns in the cost structure and operations:

Back Office (usually fastest to pilot)

  • Invoice processing, AP/AR matching, expense categorization

  • Contract abstraction — vendor agreements, leases, customer MSAs

  • Month-end close: reconciliations, flux commentary, lender reporting first drafts

Revenue / Front Office

  • RFP and proposal first drafts — big lever if revenue is project-based

  • Sales call summaries and CRM hygiene

  • Customer support ticket triage and first-response drafting

  • Quoting for configured / complex products

Operations (sector-dependent)

  • SOP and quality documentation generation

  • Scheduling and dispatch (field services, logistics)

  • Code generation and review (software portcos)

For each leverage point, capture in one line: what it replaces, FTE-hours/week saved (assume 30-50%, not 100%), and whether it's buy-off-the-shelf or needs a light build.

Step 3: Rank Across the Portfolio

Stack every leverage point from every company into one list. Rank by:

  1. Dollar impact — annualized EBITDA contribution (cost out + revenue lift, net of tool cost)

  2. Speed to value — months to first measurable result

  3. Probability — discount for data quality, change management risk, management team capability

Tiebreaker: favor opportunities with <18 months of hold period remaining — those need to move now or not at all.

Output the stack:

RankCompanyOpportunityEst. EBITDA ($)Months to ValueGateFirst Step
1Go
2Go
3Wait — [blocker]
Step 4: Find the Replays

The highest-leverage move in a portfolio is running one successful play at multiple companies. Scan for:

  • Same sector, same function — two healthcare services portcos with manual prior-auth? One implementation, two deployments.

  • Same tool, different company — if one portco already has a working invoice-processing setup, flag every other portco with >$Xm in AP volume as a fast follower.

  • Shared vendor leverage — three portcos buying the same tool is a pricing conversation.

List each replay with the lead company (who proves it) and follower companies (who copy it).

Step 5: Output

One page for the operating partner, structured for a portfolio review:

  1. Top 5 across the portfolio — the ranked table from Step 3, with owner and 30-day first step

  2. Replays — 2-3 playbooks that hit multiple companies at once

  3. Go / Wait by company — one line each; for Waits, what unblocks them

  4. What we're NOT doing — the opportunities that looked good on paper but failed a gate; saves the operating partner from relitigating them every quarter

  5. Aggregate EBITDA contribution — total portfolio-wide AI opportunity, split Year 1 quick wins vs. Years 2-3 scale

Important Notes

  • Rank by dollars, not excitement. A boring AP automation that saves $400k at a $40m revenue company beats a flashy customer-facing chatbot every time.

  • The binding constraint is almost always data, not models. If a company can't produce a clean customer list, AI isn't the first project — a data cleanup is. Say so plainly.

  • Off-the-shelf first. Custom builds are slow, expensive, and fragile for companies without engineering depth. Favor tools they can buy and deploy.

  • Ownership is the real gate. A quick win with no internal owner dies in 90 days. If no one on the management team wants it, mark it Wait regardless of the dollar size.

  • Hold period drives urgency. A company 3 years from exit can afford a foundational data project. A company 12 months out needs something that shows up in the LTM EBITDA for the CIM — or skip it.

  • Failed pilots are signal. If management already tried something and it didn't stick, find out why before proposing the same thing again.

Files

LICENSE


                                 Apache License
                           Version 2.0, January 2004
                        http://www.apache.org/licenses/

   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

   1. Definitions.

      "License" shall mean the terms and conditions for use, reproduction,
      and distribution as defined by Sections 1 through 9 of this document.

      "Licensor" shall mean the copyright owner or entity authorized by
      the copyright owner that is granting the License.

      "Legal Entity" shall mean the union of the acting entity and all
      other entities that control, are controlled by, or are under common
      control with that entity. For the purposes of this definition,
      "control" means (i) the power, direct or indirect, to cause the
      direction or management of such entity, whether by contract or
      otherwise, or (ii) ownership of fifty percent (50%) or more of the
      outstanding shares, or (iii) beneficial ownership of such entity.

      "You" (or "Your") shall mean an individual or Legal Entity
      exercising permissions granted by this License.

      "Source" form shall mean the preferred form for making modifications,
      including but not limited to software source code, documentation
      source, and configuration files.

      "Object" form shall mean any form resulting from mechanical
      transformation or translation of a Source form, including but
      not limited to compiled object code, generated documentation,
      and conversions to other media types.

      "Work" shall mean the work of authorship, whether in Source or
      Object form, made available under the License, as indicated by a
      copyright notice that is included in or attached to the work
      (an example is provided in the Appendix below).

      "Derivative Works" shall mean any work, whether in Source or Object
      form, that is based on (or derived from) the Work and for which the
      editorial revisions, annotations, elaborations, or other modifications
      represent, as a whole, an original work of authorship. For the purposes
      of this License, Derivative Works shall not include works that remain
      separable from, or merely link (or bind by name) to the interfaces of,
      the Work and Derivative Works thereof.

      "Contribution" shall mean any work of authorship, including
      the original version of the Work and any modifications or additions
      to that Work or Derivative Works thereof, that is intentionally
      submitted to Licensor for inclusion in the Work by the copyright owner
      or by an individual or Legal Entity authorized to submit on behalf of
      the copyright owner. For the purposes of this definition, "submitted"
      means any form of electronic, verbal, or written communication sent
      to the Licensor or its representatives, including but not limited to
      communication on electronic mailing lists, source code control systems,
      and issue tracking systems that are managed by, or on behalf of, the
      Licensor for the purpose of discussing and improving the Work, but
      excluding communication that is conspicuously marked or otherwise
      designated in writing by the copyright owner as "Not a Contribution."

      "Contributor" shall mean Licensor and any individual or Legal Entity
      on behalf of whom a Contribution has been received by Licensor and
      subsequently incorporated within the Work.

   2. Grant of Copyright License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      copyright license to reproduce, prepare Derivative Works of,
      publicly display, publicly perform, sublicense, and distribute the
      Work and such Derivative Works in Source or Object form.

   3. Grant of Patent License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      (except as stated in this section) patent license to make, have made,
      use, offer to sell, sell, import, and otherwise transfer the Work,
      where such license applies only to those patent claims licensable
      by such Contributor that are necessarily infringed by their
      Contribution(s) alone or by combination of their Contribution(s)
      with the Work to which such Contribution(s) was submitted. If You
      institute patent litigation against any entity (including a
      cross-claim or counterclaim in a lawsuit) alleging that the Work
      or a Contribution incorporated within the Work constitutes direct
      or contributory patent infringement, then any patent licenses
      granted to You under this License for that Work shall terminate
      as of the date such litigation is filed.

   4. Redistribution. You may reproduce and distribute copies of the
      Work or Derivative Works thereof in any medium, with or without
      modifications, and in Source or Object form, provided that You
      meet the following conditions:

      (a) You must give any other recipients of the Work or
          Derivative Works a copy of this License; and

      (b) You must cause any modified files to carry prominent notices
          stating that You changed the files; and

      (c) You must retain, in the Source form of any Derivative Works
          that You distribute, all copyright, patent, trademark, and
          attribution notices from the Source form of the Work,
          excluding those notices that do not pertain to any part of
          the Derivative Works; and

      (d) If the Work includes a "NOTICE" text file as part of its
          distribution, then any Derivative Works that You distribute must
          include a readable copy of the attribution notices contained
          within such NOTICE file, excluding those notices that do not
          pertain to any part of the Derivative Works, in at least one
          of the following places: within a NOTICE text file distributed
          as part of the Derivative Works; within the Source form or
          documentation, if provided along with the Derivative Works; or,
          within a display generated by the Derivative Works, if and
          wherever such third-party notices normally appear. The contents
          of the NOTICE file are for informational purposes only and
          do not modify the License. You may add Your own attribution
          notices within Derivative Works that You distribute, alongside
          or as an addendum to the NOTICE text from the Work, provided
          that such additional attribution notices cannot be construed
          as modifying the License.

      You may add Your own copyright statement to Your modifications and
      may provide additional or different license terms and conditions
      for use, reproduction, or distribution of Your modifications, or
      for any such Derivative Works as a whole, provided Your use,
      reproduction, and distribution of the Work otherwise complies with
      the conditions stated in this License.

   5. Submission of Contributions. Unless You explicitly state otherwise,
      any Contribution intentionally submitted for inclusion in the Work
      by You to the Licensor shall be under the terms and conditions of
      this License, without any additional terms or conditions.
      Notwithstanding the above, nothing herein shall supersede or modify
      the terms of any separate license agreement you may have executed
      with Licensor regarding such Contributions.

   6. Trademarks. This License does not grant permission to use the trade
      names, trademarks, service marks, or product names of the Licensor,
      except as required for reasonable and customary use in describing the
      origin of the Work and reproducing the content of the NOTICE file.

   7. Disclaimer of Warranty. Unless required by applicable law or
      agreed to in writing, Licensor provides the Work (and each
      Contributor provides its Contributions) on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
      implied, including, without limitation, any warranties or conditions
      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
      PARTICULAR PURPOSE. You are solely responsible for determining the
      appropriateness of using or redistributing the Work and assume any
      risks associated with Your exercise of permissions under this License.

   8. Limitation of Liability. In no event and under no legal theory,
      whether in tort (including negligence), contract, or otherwise,
      unless required by applicable law (such as deliberate and grossly
      negligent acts) or agreed to in writing, shall any Contributor be
      liable to You for damages, including any direct, indirect, special,
      incidental, or consequential damages of any character arising as a
      result of this License or out of the use or inability to use the
      Work (including but not limited to damages for loss of goodwill,
      work stoppage, computer failure or malfunction, or any and all
      other commercial damages or losses), even if such Contributor
      has been advised of the possibility of such damages.

   9. Accepting Warranty or Additional Liability. While redistributing
      the Work or Derivative Works thereof, You may choose to offer,
      and charge a fee for, acceptance of support, warranty, indemnity,
      or other liability obligations and/or rights consistent with this
      License. However, in accepting such obligations, You may act only
      on Your own behalf and on Your sole responsibility, not on behalf
      of any other Contributor, and only if You agree to indemnify,
      defend, and hold each Contributor harmless for any liability
      incurred by, or claims asserted against, such Contributor by reason
      of your accepting any such warranty or additional liability.

   END OF TERMS AND CONDITIONS

   APPENDIX: How to apply the Apache License to your work.

      To apply the Apache License to your work, attach the following
      boilerplate notice, with the fields enclosed by brackets "[]"
      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

   Copyright [yyyy] [name of copyright owner]

   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.

Requirements and compatibility

Written for: Claude Code, Claude apps

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Needs an MCP server

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Published by
Anthropic
Publisher
Anthropic (Official)
Source
anthropics/financial-services · plugins/vertical-plugins/private-equity/skills/ai-readiness · commit 6056506
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Anthropic.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download ai-readiness.zip