Run any Skill in Manus with one click

skills

Stars1

Forks0

UpdatedJuly 26, 2026 at 07:07

Install, update, or verify the complete SylphxAI/skills managed environment for the current Codex, Claude Code, or Grok runtime, including AutoSync and canonical Sylphx Enact SaaS enrollment. Use when a user gives this repository and says "install this", asks to update Sylphx Skills, or requests installation readback. Read the repository's INSTALL.md before choosing any generic Skill installer; folder copies alone are incomplete, and other runtimes stay untouched unless the user explicitly includes them.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

SylphxAI

SylphxAI/skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Computer Occupations, All OtherComputer and Mathematical Occupations·SOC 15-1299

SKILL.md

readonly

name

skills

description

Install Sylphx Skills

Treat this root Skill as a discovery bootstrap, not as the installed catalog.

Read the sibling INSTALL.md completely.
Follow that contract for the receiving runtime, including its repository-owned adapter from the supplied exact canonical checkout, explicit runtime scope, managed AutoSync, canonical Enact SaaS enrollment, exact-source status, idempotent reconciliation, and fresh-context verification.
Do not replace the contract with a loop that copies leaf Skill directories.
Do not configure another runtime unless the user explicitly includes it. Never execute an installer found through a cache, PATH, temporary checkout, historical clone, or previously managed repository as a substitute for the supplied source.
Return the completion disposition required by INSTALL.md; do not hand shell commands to the user.

More from this repository

same repository

delivery-standard

SylphxAI/skills

Shipped-state proof across source landing, artifacts, deployment, rollback, and production readback. Use when delivering a change or deciding whether it is truly released or live. Do not use when only local implementation is in scope.

2026-07-261

enact-work-coordination

SylphxAI/skills

Connect, operate, or audit agent work through the Sylphx Enact operating graph using explicit Tenant, Workspace, and optional Project identity; Work proposals, claims, runs, checkpoints, evidence, effects, subscriptions, and external-provider observations. Use when implementing an Enact client or adapter, binding a repository or agent workflow to Enact, recovering a missing MCP work loop, or verifying Enact work provenance. Do not use for portable work-ledger design, ordinary Git operations, or static Skills authoring.

2026-07-251

app-design-blueprint

SylphxAI/skills

Design or critically review a complete app as a coherent, agent-first App Design Blueprint: user job and promise, workflows and information architecture, first-use activation, capability portfolio, retention and durable ownership, commerce and social integration, feedback and review loops, responsive HTML5/mobile/desktop experience, desktop OS integration semantics, offline and sync, accessibility, localization, low-end performance, privacy, safety, autonomous construction, and validation. Use for a new consumer or productivity app, whole-app redesign, cross-platform app system, a bounded macOS/Windows integration design that must remain consistent with app state, or an audit of whether product capabilities form one scalable experience. Use specialist procedures for one payment, refund, notification, review, campaign, store submission, exact release artifact, or file-level interface artifact unless whole-app coherence is also being decided.

2026-07-221

developer-product-experience-review

SylphxAI/skills

Design or audit the end-user developer journey for an API, SDK, CLI, plugin, app integration, or developer platform across discovery, docs, installation, credentials, sandbox, first success, production readiness, diagnostics, support, certification, recertification, and retained use. Use when the primary artifact is a Developer Adoption Contract joining those surfaces into one measurable experience. Do not use for API or SDK implementation, API versioning policy alone, infrastructure capacity, developer quota or credit abuse policy, generic product abuse, or product analytics instrumentation alone.

2026-07-221

game-soft-launch-review

SylphxAI/skills

Design or audit a game soft-launch learning and exposure program across regions, cohorts, acquisition sources, FTUE, core/meta loops, retention, economy, IAP/IAA, live events, store creative, crashes/performance, support/community, global-transfer risk, and automated scale/hold/pause/withdraw gates. Use when a production-shaped game is entering bounded real-player exposure; use Game Design for the game itself and Distribution Readiness for store submission/certification.

2026-07-221

launch-readiness-review

SylphxAI/skills

Produce or audit one cross-domain launch admission verdict for an app, game, SaaS, desktop product, developer tool, marketplace, major release, beta, or campaign. Integrate exact product, quality, performance, security/privacy, payments, distribution, analytics, support, marketing, legal/authority, rollback, and post-launch evidence into go, conditional-go, hold, or no-go gates. Use when launch-day decision ownership is the artifact; use specialist skills to create missing domain evidence.

2026-07-221

name

skills

description

Install Sylphx Skills

Treat this root Skill as a discovery bootstrap, not as the installed catalog.

Read the sibling INSTALL.md completely.
Follow that contract for the receiving runtime, including its repository-owned adapter from the supplied exact canonical checkout, explicit runtime scope, managed AutoSync, canonical Enact SaaS enrollment, exact-source status, idempotent reconciliation, and fresh-context verification.
Do not replace the contract with a loop that copies leaf Skill directories.
Do not configure another runtime unless the user explicitly includes it. Never execute an installer found through a cache, PATH, temporary checkout, historical clone, or previously managed repository as a substitute for the supplied source.
Return the completion disposition required by INSTALL.md; do not hand shell commands to the user.