pick-cloud-services

Choose and lock a cloud service category with a dated decision record.

Updated Apr 28, 2026

Search Tags:#decision making #infrastructure #service selection #cloud services #decision locking

Ready to run

npx skills add https://github.com/dformoso/positronic --skill pick-cloud-services

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pick-cloud-services
Source: https://github.com/dformoso/positronic/tree/main/skills/defining/pick-cloud-services
Command: npx skills add https://github.com/dformoso/positronic --skill pick-cloud-services

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill assists in choosing the right external or cloud service for various categories, from hosting to payments, based on live research, and locking the decision as a dated record.

Core Features & Use Cases

Live Research: Offers a way to pick cloud services from a live research perspective rather than relying on memory.
Decision Locking: Locks the decision as a dated record for future reference and review.
Re-pick and Greenfield Projects: Useful for re-picking services due to vendor changes or for new projects to decide the development-to-production path.
Category-Specific Guidance: Provides specific questions and criteria for each category like compute, database, cache, and more.

Quick Start

Run the pick-cloud-services skill to choose a hosting provider and lock the decision record.

Frequently Asked Questions about pick-cloud-services

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I choose the right cloud services for my infrastructure categories?▼

You select cloud services by applying live research and category-specific criteria for infrastructure like compute, database, or hosting. This ensures an validated choice locked as a dated decision record for future reference.

What is a dated decision record for cloud service selection?▼

A dated decision record locks your chosen cloud service at a specific time. It captures the live research and validation behind the infrastructure choice, providing a historical reference for future review or vendor changes.

Can I use this approach to re-pick a hosting provider after a vendor change?▼

Yes, you can re-pick a hosting provider or database after vendor changes. The process uses live research rather than memory to evaluate new options and updates your record with the newly locked infrastructure choice.

How do I validate a cloud infrastructure pick for a greenfield project?▼

You validate a cloud infrastructure pick for a greenfield project by applying category-specific questions and live research. This assesses the development-to-production path and locks the validated service choice into a decision record.

Does this method require live research for selecting a payment provider?▼

Yes, selecting a payment provider requires live research to ensure current market validity. This research feeds into the decision validation process before the payment service choice is locked as a dated record.

What are the limitations of relying on memory for database service selection?▼

Relying on memory for database service selection risks outdated information on vendor capabilities and pricing. Live research prevents this by validating current data before locking the infrastructure decision as a record.