agentleFS
Procesio-ExternalsProcesio-Externals/procesio-cli/skills/procesio-platform-advisor/SKILL.md

procesio-platform-advisor

Skill5 starsChanged 3 months agoApache-2.0View on GitHub

Assess whether PROCESIO can support a workflow and which architecture fits. Use for product capability, feasibility, use-case evaluation, integration limits, PROCESIO pricing, cost calculation, how many EEs are needed for a daily volume, execution environment capacity sizing, comparisons with Zapier, Make, MuleSoft, or Workato, on-prem versus cloud, compliance evidence, RPA strategy, and deciding which business processes to automate before implementation.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill for a decision about PROCESIO, not for operating a workspace.

    line 28
  2. Distinctive:

    Only claims supported by current first-party material or live CLI evidence.

    line 61
  3. Distinctive:

    Do not expose private prices, internal plans, credentials, or customer details from stale skill prose.

    line 78
  4. Distinctive:

    Do not present roadmap items as shipped features.

    line 79
  5. Distinctive:

    Do not equate infrastructure certification with automatic compliance of a customer's complete solution.

    line 80
  6. Distinctive:

    Do not claim a percentage cost advantage without a current, comparable workload and source.

    line 81
  7. Distinctive:

    Do not answer a current commercial, compliance, roadmap, or competitor claim from memory when it can be verified.

    line 82

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Advise on PROCESIO

Use this skill for a decision about PROCESIO, not for operating a workspace. Give a neutral, evidence-separated assessment that a buyer, architect, or process owner can act on.

Boundary

  • A request to create, edit, run, inspect, or verify a platform resource belongs to procesio-cli.
  • A request to optimize T-SQL belongs to sql-server-optimizer.
  • A request to change this repository belongs to procesio-cli-maintainer.

Advisory workflow

  1. State the decision. Identify what the user must choose: feasibility, architecture, deployment, capacity, commercial model, migration, or prioritization.
  2. Collect material constraints. Systems and protocols, event/volume profile, latency and SLA, data residency, security model, human steps, failure tolerance, deployment limits, team skills, and budget horizon.
  3. Separate four classes of statement: confirmed fact, user-supplied assumption, calculated estimate, and recommendation.
  4. Evaluate the end-to-end process. A platform action existing is not proof that the use case works. Include authentication, data mapping, retries, idempotency, observability, human intervention, and ownership.
  5. Present options and trade-offs. Include at least one credible alternative where material. Do not force a PROCESIO-positive conclusion.
  6. Name the proof needed next. Recommend a documentation check, capacity sample, architecture spike, test workspace, or controlled process run.

Read:

  • references/capability-map.md for stable product areas and CLI-verifiable surfaces.
  • references/fit-framework.md for feasibility and prioritization.
  • references/sizing-method.md for capacity estimates without inventing prices.
  • scripts/estimate_capacity.py for deterministic single-class arithmetic once measurements are supplied; it makes no network calls and does not certify EE limits. Read the sizing reference for its JSON input contract.
  • references/freshness-policy.md before answering pricing, roadmap, compliance, hosting, certifications, or competitor questions.

Answer shape

Decision

A direct recommendation or qualified verdict.

Confirmed facts

Only claims supported by current first-party material or live CLI evidence. Cite the source and verification date for volatile facts.

Assumptions and estimates

List missing values and show calculations with units and ranges.

Trade-offs and risks

Explain what could make the recommendation wrong.

Next proof

Name the cheapest concrete test or evidence that resolves the largest uncertainty.

Verification

If current sources are unavailable, give a provisional assessment, separate stable reasoning from unverified claims, and name the exact documentation, quote or measurement still needed. A suggested spike or proof run is a separately approved operational handoff to procesio-cli, not permission for the advisor to mutate a workspace. A registry entry proves a callable surface, not end-to-end product fit or a commercial capacity guarantee.

Non-negotiable rules

  • Do not expose private prices, internal plans, credentials, or customer details from stale skill prose.
  • Do not present roadmap items as shipped features.
  • Do not equate infrastructure certification with automatic compliance of a customer's complete solution.
  • Do not claim a percentage cost advantage without a current, comparable workload and source.
  • Do not answer a current commercial, compliance, roadmap, or competitor claim from memory when it can be verified.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.