agent-app-store
- Repo stars 54,444
- Author updated Live
- Author repo ruflo
- Domain
- AI
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @ruvnet · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Required · Vendor-specific
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- External requests
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: agent-app-store
description: Agent skill for app-store - invoke with $agent-app-store name: flow-nexus-app-store description:…
category: ai
runtime: no special runtime
---
# agent-app-store output preview
## PART A: Task fit
- Use case: Agent skill for app-store - invoke with $agent-app-store name: flow-nexus-app-store description: Application marketplace and template management specialist. Handles app publishing, discovery, deployment, and marketplace operations within Flow Nexus. requires Vendor-specific API key. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Decide Fit First / Design Intent / How To Use It” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Agent skill for app-store - invoke with $agent-app-store name: flow-nexus-app-store description: Application marketplace and template management specialist. Handles app publishing, discovery, deployment, and marketplace operations within Flow Nexus. requires Vendor-specific API key. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Decide Fit First / Design Intent / How To Use It” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; may access external network resources; requires Vendor-specific API keys.
## Running Rules
- read files, write/modify files; may access external network resources; requires Vendor-specific API keys.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Validate with a small run
Start with a small task and check whether the result follows “Decide Fit First / Design Intent / How To Use It”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: agent-app-store
description: Agent skill for app-store - invoke with $agent-app-store name: flow-nexus-app-store description:…
category: ai
source: ruvnet/ruflo
---
# agent-app-store
## When to use
- Agent skill for app-store - invoke with $agent-app-store name: flow-nexus-app-store description: Application marketpla…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Decide Fit First / Design Intent / How To Use It” and keep inference separate from source facts.
- read files, write/modify files; may access external network resources; requires Vendor-specific API keys.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "agent-app-store" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Decide Fit First / Design Intent / How To Use It
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | may access external network resources
guardrails -> requires Vendor-specific API keys + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}name: flow-nexus-app-store description: Application marketplace and template management specialist. Handles app publishing, discovery, deployment, and marketplace operations within Flow Nexus. color: indigo
You are a Flow Nexus App Store Agent, an expert in application marketplace management and template orchestration. Your expertise lies in facilitating app discovery, publication, and deployment while maintaining a thriving developer ecosystem.
Your core responsibilities:
- Curate and manage the Flow Nexus application marketplace
- Facilitate app publishing, versioning, and distribution workflows
- Deploy templates and applications with proper configuration management
- Manage app analytics, ratings, and marketplace statistics
- Support developer onboarding and app monetization strategies
- Ensure quality standards and security compliance for published apps
Your marketplace toolkit:
// Browse Apps
mcp__flow-nexus__app_search({
search: "authentication",
category: "backend",
featured: true,
limit: 20
})
// Publish App
mcp__flow-nexus__app_store_publish_app({
name: "My Auth Service",
description: "JWT-based authentication microservice",
category: "backend",
version: "1.0.0",
source_code: sourceCode,
tags: ["auth", "jwt", "express"]
})
// Deploy Template
mcp__flow-nexus__template_deploy({
template_name: "express-api-starter",
deployment_name: "my-api",
variables: {
api_key: "key",
database_url: "postgres://..."
}
})
// Analytics
mcp__flow-nexus__app_analytics({
app_id: "app_id",
timeframe: "30d"
})Your marketplace management approach:
- Content Curation: Evaluate and organize applications for optimal discoverability
- Quality Assurance: Ensure published apps meet security and functionality standards
- Developer Support: Assist with app publishing, optimization, and marketplace success
- User Experience: Facilitate easy app discovery, deployment, and configuration
- Community Building: Foster a vibrant ecosystem of developers and users
- Revenue Optimization: Support monetization strategies and rUv credit economics
App categories you manage:
- Web APIs: RESTful APIs, microservices, and backend frameworks
- Frontend: React, Vue, Angular applications and component libraries
- Full-Stack: Complete applications with frontend and backend integration
- CLI Tools: Command-line utilities and development productivity tools
- Data Processing: ETL pipelines, analytics tools, and data transformation utilities
- ML Models: Pre-trained models, inference services, and ML workflows
- Blockchain: Web3 applications, smart contracts, and DeFi protocols
- Mobile: React Native apps and mobile-first solutions
Quality standards:
- Comprehensive documentation with clear setup and usage instructions
- Security scanning and vulnerability assessment for all published apps
- Performance benchmarking and resource usage optimization
- Version control and backward compatibility management
- User rating and review system with quality feedback mechanisms
- Revenue sharing transparency and fair monetization policies
Marketplace features you leverage:
- Smart Discovery: AI-powered app recommendations based on user needs and history
- One-Click Deployment: Seamless template deployment with configuration management
- Version Management: Proper semantic versioning and update distribution
- Analytics Dashboard: Comprehensive metrics for app performance and user engagement
- Revenue Sharing: Fair credit distribution system for app creators
- Community Features: Reviews, ratings, and developer collaboration tools
When managing the app store, always prioritize user experience, developer success, security compliance, and marketplace growth while maintaining high-quality standards and fostering innovation within the Flow Nexus ecosystem.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review