Agent Skills: renewal-manager
Expert renewal management guidance for maximizing retention and expansion revenue. Use when building renewal playbooks, forecasting renewal pipeline, structuring multi-year deals, developing pricing strategies, mitigating churn risk, defending against competitive displacement, negotiating contracts, attaching expansion to renewals, or optimizing renewal operations. Covers high-touch and tech-touch renewal motions, early renewal strategies, and save plays.
ID: ncklrs/startup-os-skills/renewal-manager
Install this agent skill to your local
Skill Files
The files that make up renewal-manager.
Loading file tree…
More agent skills
- quill-codeEdit the @posthog/quill design system locally and consume the change in products/desktop before it is published to npm. Use when changing quill components/primitives/tokens, when a quill change must be tested inside the Code app, or when the user mentions quill, the design system, the .local-quill tarball, or the @posthog/quill pnpm override.
- woocommerce-code-reviewReview WooCommerce code changes for coding standards compliance. Use when reviewing code locally, performing automated PR reviews, or checking code quality.
- commitCreate a git commit with conventional commit format. MUST use anytime you want to commit changes.
- adopting-generated-api-typesUse when migrating frontend code from manual API client calls (`api.get`, `api.create`, `api.surveys.get`, `api.dashboards.list`, `new ApiRequest()`) and handwritten TypeScript interfaces to generated API functions and types. Triggers on files importing from `lib/api`, files with `api.get<`, `api.create<`, `api.<entity>.<method>`, manual interface definitions that duplicate backend serializers, or any frontend file that constructs API URLs by hand. Covers the full replacement workflow — finding the generated equivalent, swapping imports, adapting call sites, and removing dead manual types.
- edge-candidate-agentGenerate and prioritize US equity long-side edge research tickets from EOD observations, then export pipeline-ready candidate specs for trade-strategy-pipeline Phase I. Use when users ask to turn hypotheses/anomalies into reproducible research tickets, convert validated ideas into `strategy.yaml` + `metadata.json`, or preflight-check interface compatibility (`edge-finder-candidate/v1`) before running pipeline backtests.
- visualization-settingsChoosing a card's `display` and authoring `visualization_settings` for question_write and patch_dashcard — which chart fits which data shape, the output-column-name rule, minimum keys per chart family, map regions, the column_settings JSON-string-key footgun. Triggers — "make this a bar/line/pie chart", "what chart should I use", "format as currency", "the card renders as a table instead of a chart", "conditional formatting", "region map".