agentsclimarketplace

Monocloud quickstart

Skill monocloud/agent-skills/plugins/monocloud/skills/monocloud-quickstart

Official MonoCloud Agent Skills repository.

Install
npx -y skills add monocloud/agent-skills --skill monocloud-quickstart

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use this skill FIRST whenever a user asks to add MonoCloud (authentication or management) to a project but hasn't said which framework. It detects the project type by reading `package.json`, `*.csproj`, `requirements.txt`, etc., then routes to the correct framework-specific MonoCloud skill (`monocloud-auth-nextjs`, `monocloud-auth-react`, `monocloud-auth-express`, `monocloud-auth-fastify`, `monocloud-auth-aspnetcore`, `monocloud-web-js`, `monocloud-management-js`, `monocloud-management-dotnet`). Also use when the user says "set up MonoCloud", "add MonoCloud login", "integrate MonoCloud", "use the MonoCloud SDK", or "manage users programmatically with MonoCloud" without naming a stack.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

6.2 KB, ~1.5k tokens by cl100k_base, as published. Nobody here has run it

MonoCloud Quickstart Router

This skill detects the project's stack and points you at the correct MonoCloud skill. Do not try to write integration code from this skill — load the framework-specific skill and follow its SKILL.md.

Step 1 — Detect the framework

Run the bundled detector. It scans the working directory (or a path you pass) and prints the recommended skill plus its reasoning:

node scripts/detect.js              # current dir
node scripts/detect.js /path/to/app

The detector handles these signals:

Signal in projectSkill to use
"next" in package.json dependenciesmonocloud-auth-nextjs
"@monocloud/auth-nextjs" already installedmonocloud-auth-nextjs
"@monocloud/auth-react" already installedmonocloud-auth-react
"@monocloud/auth-web-js" already installedmonocloud-web-js
"@monocloud/management" already installedmonocloud-management-js
"fastify" in package.json (no next)monocloud-auth-fastify
"express" in package.json (no next/fastify)monocloud-auth-express
"react" + browser bundler (vite/CRA/parcel/webpack) and no server frameworkmonocloud-auth-react
Browser SPA with vite/parcel/webpack/rollup and no server framework (no React)monocloud-web-js
*.csproj referencing MonoCloud.Authentication.Apimonocloud-auth-aspnetcore
*.csproj referencing MonoCloud.Managementmonocloud-management-dotnet
*.csproj with no MonoCloud package — ASP.NET Core web/API project (Sdk="Microsoft.NET.Sdk.Web" / references Microsoft.AspNetCore.*)monocloud-auth-aspnetcore (to protect the API) — use monocloud-management-dotnet instead if the goal is programmatic tenant/user management
Any other *.csproj (no MonoCloud yet, non-web .NET)monocloud-management-dotnet (likely programmatic management) — use monocloud-auth-aspnetcore if it's actually an API to protect

If two skills could apply (e.g. an Express API in a Next.js monorepo), prefer the more specific match in the app or package you're editing, not the workspace root.

Step 2 — Confirm with the user (only if ambiguous)

If detection is ambiguous (e.g. multiple package.json files in a monorepo, or both "express" and "@monocloud/management" declared), ask the user which app they want to wire up before proceeding.

Step 3 — Load the framework skill

Once you know which skill to use, stop reading this file and switch to that skill's SKILL.md. The framework skill owns:

  • Installation command
  • Environment variables (these differ per SDK — see "Env-var families" below)
  • File layout (middleware/proxy location, DI registration, etc.)
  • Code patterns
  • Troubleshooting

Env-var families (for quick reference)

MonoCloud uses prefix-namespaced env vars per SDK. Don't mix them.

PrefixSDK
MONOCLOUD_AUTH_*@monocloud/auth-nextjs (frontend / Next.js session auth)
MONOCLOUD_BACKEND_*@monocloud/backend-node/{express,fastify} (API token validation)
MONOCLOUD_MANAGEMENT_*@monocloud/management (JS Management API SDK)
MonoCloud:Management:* (config keys, not env)MonoCloud.Management (.NET Management API SDK)
(none)MonoCloud.Authentication.Api — ASP.NET Core API auth, configured via AddMonoCloudAuthentication(options => …) / IConfiguration binding only
(none)@monocloud/auth-web-js — pure browser SDK, configured via constructor options only
(none)@monocloud/auth-react — React SPA SDK, configured via <MonoCloudAuthProvider> props only

Skills catalog

  • monocloud-auth-nextjs — Sign-in/sign-up, sessions, route protection, components, hooks for Next.js (App + Pages Router).
  • monocloud-auth-react — @monocloud/auth-react — React SPA SDK: <MonoCloudAuthProvider>, useAuth, <SignIn>/<SignOut>/<Protected> components.
  • monocloud-auth-express — JWT / introspection token validation, scope + group enforcement for Express APIs.
  • monocloud-auth-fastify — Same engine as above, with a Fastify onRequest hook.
  • monocloud-auth-aspnetcore — MonoCloud.Authentication.Api — ASP.NET Core access-token validation (JWT + introspection), scope/group authorization via [Authorize] policies, IIntrospectionCache caching, mTLS certificate-bound tokens.
  • monocloud-web-js — @monocloud/auth-web-js — browser SDK for vanilla JS / TS SPAs: redirect/popup/silent flows, sessions, pluggable storage.
  • monocloud-management-js — @monocloud/management — programmatic admin: users, clients, groups, resources, keys, logs, options, branding, trust stores.
  • monocloud-management-dotnet — MonoCloud.Management NuGet — same surface in .NET with DI registration.

Don't guess — verify after wiring

After the framework skill has been applied, run that skill's diagnostic:

node skills/<skill-folder>/scripts/verify.js

For example: node skills/monocloud-auth-nextjs/scripts/verify.js. The diagnostic checks env vars and that the SDK appears in package.json.

Deeper reference

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.