mergesort/recap-integration
.agents/skills/recap-integration/SKILL.md
Integrates the Recap Swift package into SwiftUI apps, authors Recap-compatible releases markdown, and configures RecapDisplayPolicy and RecapScreen customization. Use when adding Recap into an app, updating Releases.md, or customizing the behavior of a Recap screen.
$ install --global
skillsauthnpx skillsauth add mergesort/Recap recap-integrationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 15, 2026, 11:55 PM13.0s1 file scanned
SKILL.md
- name:
- recap-integration
- description:
- Integrates the Recap Swift package into SwiftUI apps, authors Recap-compatible releases markdown, and configures RecapDisplayPolicy and RecapScreen customization. Use when adding Recap into an app, updating Releases.md, or customizing the behavior of a Recap screen.
Recap Integration
Use this skill when integrating, configuring, or using the Recap library.
What to read first
Start with these files:
README.mdSources/Recap/Public/RecapScreen.swiftSources/Recap/Public/View+Recap.swiftSources/Recap/Public/RecapDisplayPolicy.swiftSources/Recap/Public/RecapDisplayPolicy.Trigger.swiftDemo/Demo/Assets/Releases.mdDemo/Demo/DemoRecapScreen.swift
Read additional public API files in Sources/Recap/Public/ only if the task touches a specific type.
Core workflow
- Identify whether the task is about integration, release authoring, display policy, or screen customization.
- Prefer Recap's public APIs over custom implementations.
- Match existing Recap naming and examples from the README and demo app.
- Keep examples and release content user-facing and concise.
Integration rules
- Prefer
ReleasesParser(fileName:)for bundled release markdown. - Prefer
RecapScreen(releases:)as the entry point for presentation. - Prefer
RecapDisplayPolicyandRecapDisplayPolicy.Triggerover hand-rolled version gating. - Prefer
.recapScreenPaginationStyle(.automatic)unless the user explicitly wants forced.labeledor.compact. - When customizing behavior, use
View+Recapmodifiers instead of editing internal implementation unless the task is explicitly a library change.
Release markdown rules
When creating or editing a Recap releases markdown file:
- Keep the newest release first.
- Follow the schema documented in
README.md. - Use one release section per app version.
- Use user-facing feature titles and descriptions, not commit-style summaries.
- Choose the semantic change type (
Major,Minor,Patch) based on product impact, not commit count. - Reuse the style and structure of
Demo/Demo/Assets/Releases.md.
Mac Catalyst guidance
If the task touches Mac Catalyst:
- Preserve the distinction between automatic pagination, labeled buttons, and compact buttons.
- Be careful not to regress iPhone or iPad behavior while changing Catalyst presentation.
Avoid
- Do not invent a different release markdown format.
- Do not parse releases manually if
ReleasesParseris sufficient. - Do not replace
RecapDisplayPolicywith custom version-comparison logic unless the user explicitly needs behavior outside the public API.
Related Skills
openclaw/taskflow
tools
VerifiedTrustedCommunity
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
357,764SKILL.mdUpdated Apr 10, 2026
openclaw/extensions/lobster
tools
VerifiedTrustedCommunity
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------
357,764SKILL.mdUpdated Apr 10, 2026
steipete/extensions/lobster
tools
VerifiedTrustedCommunity
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------
357,588SKILL.mdUpdated Apr 13, 2026
steipete/xurl
tools
VerifiedTrustedCommunity
A CLI tool for making authenticated requests to the X (Twitter) API. Use this skill when you need to post tweets, reply, quote, search, read posts, manage followers, send DMs, upload media, or interact with any X API v2 endpoint.
356,423SKILL.mdUpdated Apr 13, 2026