The new Use Model shortcut in Apple Shortcuts opens up a lot of possibilities. For example, I like to summarize a lot of pages. Sometimes, ChatGPT can’t get the text for those pages, or I don’t trust the text it retrieves. There’s a shortcut that will retrieve the cleaned up text of a page (as markdown). So, you can get that markdown, and with the new Use Model shortcut, you can summarize it and then send the markdown summary to Drafts. You could open the text up in another app to view, whatever you like, but as you can imagine, I like to catalog this stuff. Also, it can generate a little link to include for my newsletters link list.

You put this in your Sharesheet, and now when you’re reading the World Wide Web, you can get summaries real quick-like.

Here is the shortcut:

I left in the stop and output for debugging, but I’d take that out.

Here is output from one of my articles:

---

Developers Aren’t Using Your Platform? Marketing Might Be the Missing Link

Source summarized: Driving Platform Adoption: The Missed Opportunity of Marketing.

Internal Developer Platforms (IDPs) often fail to gain traction despite delivering exactly what engineers request. This piece argues that platform marketing—alongside product management and community building—is the missing discipline most teams ignore, and offers a systematic approach to drive developer adoption.

Key Insights

• Define your developer audience narrowly before pushing adoption efforts.
• Craft messaging that focuses on developer benefits, not platform features.
• Position your platform in clear, specific contexts (cloud-native apps, AI workloads, regulated environments).
• Lead with value propositions that are measurable, like time savings and frictionless onboarding.
• Avoid the “platform for everything” trap; targeted positioning accelerates adoption.
• Integrate marketing with product management for tighter feedback loops.
• Use developer-friendly proof points (fast deployments, pre-approved services, reduced ticketing).
• Iterate adoption starting with a few archetypical teams before scaling org-wide.

---

Most organizations spend years building internal platforms that meet developers’ stated needs, only to watch usage stagnate. Teams often assume technical excellence alone will win hearts and minds. The authors note that marketing—treated as a rigorous engineering-like discipline—can bridge that gap by creating awareness, clarity, and trust. The first step is laser-focusing on the actual developer persona who will use the platform. “Developers” is too broad; target application developers in specific business domains and technology stacks to avoid generic messaging.

Messaging, positioning, and value propositions form the backbone of platform marketing. Messaging should translate features into developer-relevant benefits: zero setup time, fewer meetings, and faster deployments. Positioning narrows the platform’s role in the ecosystem—rather than claiming to be universal, identify where the platform delivers the most leverage, from legacy modernization to AI-driven applications. Value propositions then provide concrete, provable outcomes, like cutting deployment cycles from days to minutes or eliminating 80% of security review meetings.

Finally, the authors emphasize that platform marketing is not fluff—it’s how you engineer adoption as deliberately as you design pipelines. By starting small, learning from early adopter teams, and communicating benefits in precise, outcome-driven language, organizations can finally capture the ROI on their internal platform investments. Marketing is not a side hustle; it’s the connective tissue that transforms a platform from shelfware into a strategic asset.

• 🤖Driving Platform Adoption: The Missed Opportunity of Marketing – Explores why technically excellent internal developer platforms still fail and how adopting structured, developer-focused marketing can dramatically improve adoption.

Summarized by ChatGPT on Sep 16, 2025 at 1:09 PM.

---

Fantastic! I used to have to do this manually.

And, are the summaries good? They’re not always perfect, but I’m often looking to see if I should spend the time to read the whole thing, especially if it’s long and…not the best of writing.