Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

semoss-ai-repo

Étoiles2

Forks0

Mis à jour19 juin 2026 à 13:52

Use when submitting a SEMOSS app into the review/repository pipeline with the ai-repo CLI — logging in, registering an app (create-app), publishing a zipped version (publish), and checking workflow status (status, versions). Covers the command set, publish gotchas (build first, what gets zipped, what's excluded), and where credentials are stored. Assumes the ai-repo binary is already installed. Do not use for iterating against a live instance (that's scripts/claude/semoss_asset_sync.py — see semoss-deploy) or for manual UI zip uploads.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

SEMOSS

SEMOSS/Template

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name

semoss-ai-repo

description

ai-repo CLI — Submit Tier

ai-repo is a CLI for the AI Repository submit/review pipeline: login, app registration, zip publishing, and status checks against the SEMOSS repository server. This is the Submit deploy tier — distinct from the Iterate tier (semoss_asset_sync.py), which updates an app's code against a running instance. Use ai-repo to push a version into the review workflow.

This skill assumes the ai-repo binary is already installed and on your PATH (installing/building the CLI itself is out of scope — see the ai-repo project's own docs). Verify with ai-repo --version.

Commands

Run ai-repo --help or ai-repo <command> --help for current flags — don't trust a copied flag list here, it drifts. The command set:

login / logout — authenticate against a <semoss-url>/Monolith base URL with an access/secret key pair.
create-app — register app metadata (name, business unit, etc.); returns a server-generated appId to hand to publish. No zip is uploaded.
publish — zip the current project and upload it as a new version.
status / versions — check the review-workflow status of a published version.

`publish` gotchas

Build first. The CLI zips and uploads from the project root — it does not run a build. Run cd client && pnpm build before publishing.
Default zipped dirs (any that exist): client/, java/, portals/, py/, mcp/. Use the include flag to add paths like semoss_config or scripts.
Always excluded, even nested: node_modules/, .git/, and secret/local files (.env, .env.*, *.local, *.local.*) — so your gitignored env config won't ship.
Use the dry-run flag to stage the zip and print its contents without uploading.

Credential storage

ai-repo login persists your secret key to ~/.ai-repo/credentials.json (mode 0600), so you only log in once. You don't manage this file by hand — login/logout handle it.

Plus depuis ce dépôt

même dépôt

semoss-user-menu

SEMOSS/Template

Use when adding a logged-in user menu, profile dropdown, logout button, or a top navigation bar to a SEMOSS app. Covers installing the shadcn/ui dropdown-menu primitive (@radix-ui/react-dropdown-menu), building a UserProfileMenu (shows the user name + logout), a MainNavigation bar, and rendering the nav inside InitializedLayout. Assumes auth is already wired (AuthProvider/useAuth, LoginPage, AuthorizedLayout — shipped in the template). Do not use for the login flow itself (already in the base) or for shadcn setup in general.

2026-06-232

semoss-deploy

SEMOSS/Template

Use when publishing, uploading, or updating a SEMOSS app — choosing among the three deploy tiers (manual UI zip, the semoss_asset_sync.py iterate flow, or the ai-repo submit pipeline), switching between named environments (local/preprod/prod), writing client/.env.local before a build, or handling SSL/proxy errors during upload. Do not use for the ai-repo CLI command reference specifically (see semoss-ai-repo) or for editing tool manifests (see semoss-mcp-manifest).

2026-06-212

semoss-mcp-manifest

SEMOSS/Template

Use when adding, editing, or wiring up a SEMOSS MCP tool manifest — mcp/py_mcp.json (Python tools) or mcp/pixel_mcp.json (Java reactors). Covers the manifest schema, the _meta fields (resourceURI, SMSS_MCP_EXECUTION, displayLocation, loadingMessage), mapping a tool's resourceURI to a hash route in Router.tsx, default vs custom UI, and when to fall back to the MakePythonMCP/MakePixelMCP regenerator reactors. Do not use for the deploy/upload flow (see semoss-deploy) or writing the tool logic itself (Java reactor / Python tool rules live in CLAUDE.md).

2026-06-212

semoss-platform-backend

SEMOSS/Template

Use when working with the SEMOSS platform control plane via the connected MCP servers — creating/publishing/tagging projects (Semoss_project_manager), creating/querying databases and fetching schema (Semoss_database_helper), or pulling platform guidance (Semoss_Platform_Instructions). Covers the project lifecycle, the MCP project tag that gates Playground-chat visibility, standalone-vs-MCP app modes, and which of the platform MCP's frontend claims to ignore. Do not use for in-app SDK calls from React (see CLAUDE.md + the engine skills) or for the deploy mechanics (see semoss-deploy).

2026-06-212

semoss-database

SEMOSS/Template

Use when writing code in an app that queries a relational or graph database on the platform, running SELECTs, inserts, updates, deletes, or fetching schema/table structure. Covers the SqlQuery(), SqlQueryBase64(), and GetDatabaseTableStructure() pixel commands via the Semoss SDK, plus listing databases with MyEngines(engineTypes=["DATABASE"]). Do not use for LLM calls (see semoss-model) or vector database queries (see semoss-vector).

2026-06-112

semoss-model

SEMOSS/Template

Use when writing code in an app that calls an LLM, embedding model, or other model engine, OR when listing/selecting models the user has access to. Covers the LLM() and MyEngines() pixel commands via the Semoss SDK, including prompt/completion calls, conversational history, image inputs, and parsing model responses. Do not use for vector database queries (see semoss-vector) or raw SQL/graph queries (see semoss-database).

2026-06-112

name

semoss-ai-repo

description

ai-repo CLI — Submit Tier

Commands

Run ai-repo --help or ai-repo <command> --help for current flags — don't trust a copied flag list here, it drifts. The command set:

login / logout — authenticate against a <semoss-url>/Monolith base URL with an access/secret key pair.
create-app — register app metadata (name, business unit, etc.); returns a server-generated appId to hand to publish. No zip is uploaded.
publish — zip the current project and upload it as a new version.
status / versions — check the review-workflow status of a published version.

`publish` gotchas

Build first. The CLI zips and uploads from the project root — it does not run a build. Run cd client && pnpm build before publishing.
Default zipped dirs (any that exist): client/, java/, portals/, py/, mcp/. Use the include flag to add paths like semoss_config or scripts.
Always excluded, even nested: node_modules/, .git/, and secret/local files (.env, .env.*, *.local, *.local.*) — so your gitignored env config won't ship.
Use the dry-run flag to stage the zip and print its contents without uploading.

Credential storage

ai-repo login persists your secret key to ~/.ai-repo/credentials.json (mode 0600), so you only log in once. You don't manage this file by hand — login/logout handle it.