Loading...
Loading...
Found 98 Skills
Report the health, performance, resource status, and actual costs of applications deployed by qianwenai-deploy to the Alibaba Cloud China site (aliyun.com) in natural language, without entering the console. Read the .qianwenai-deploy state file in the project directory to identify the application and its ECS (and optional RDS MySQL) resources, then call read-only cloud APIs to summarize application availability, ECS/RDS performance, and costs in RMB. Use cases: users ask how a deployed application is running, want a health/performance/cost overview, are concerned about CPU/memory/connection count/slow SQL risks, or ask about the monthly cost of an application deployed by qianwenai. Non-use cases: there is no .qianwenai-deploy state file; the target is the Alibaba Cloud international site (use qwencloud-observe); or the user wants to change or restore resources (use qianwenai-operate).
Diagnose why an application deployed by qianwenai-deploy to the Aliyun China site (aliyun.com) is unavailable or significantly slower, and perform a safe recovery only after the user explicitly confirms it. Read the .qianwenai-deploy state file in the project directory to identify ECS (and optionally RDS MySQL) resources, begin with minimal read-only diagnostics, and then propose only one recovery action at a time (starting the ECS instance, restarting the application service, or reloading Nginx), explaining the impact and obtaining confirmation before each action. Use cases: the user says the application will not open / returns 502 / cannot connect to the database, or requests a restart and confirmation that the application has recovered. Do not use: there is no .qianwenai-deploy state file; the target is the Aliyun International site (use qwencloud-operate); or the user only wants a status/cost overview (use qianwenai-observe).
Directly connect to the Agent Submission API (POST {base}/submit-activity-work) of the Huawei Cloud Open Capabilities Online Challenge (activity_code=open-capability-2026-1024), use AK/SK request headers (X-HW-AK / X-HW-SK / X-HW-Security-Token) to automatically submit the work link/public address generated by the activity to the two milestones, “Sandbox Deployment” (milestone=beginner) and “Persistent ECS Deployment” (milestone=intermediate), and report the corresponding points earned after each successful submission; after Sandbox Deployment (beginner), always ask the user whether they optionally want to publish the work to the Challenge Activity in the Developer Works Gallery; if it has not been published at that point, ask again after ECS (intermediate) is completed, and if it has already been published, do not ask again during the ECS phase (npx skills add ... publish-work-to-gallery). Use when the user asks to submit work, submit challenge results, automatically submit activity results, or submit a sandbox link/public address, or when a generated sandbox URL needs to be submitted for the Huawei Cloud Open Capabilities Challenge. This skill always uses the production (live) API and must not switch environments. It is only for calling APIs and does not involve any page/browser operation.
Build and review turn-based Rust game flow using turn-state enums, phase-specific schedules, intent messages, movement resolution, combat resolution, wait actions, and win/loss states. Use when implementing roguelike turns, tactical action order, ECS message entities, or decoupled input and action systems.
Scaffolds new Terraform modules with standardized structure including main.tf, variables.tf, outputs.tf, versions.tf, and README.md. This skill should be used when users want to create a new Terraform module, set up module structure, or need templates for common infrastructure patterns like VPC, ECS, S3, or RDS modules.
Builds, deploys, manages, debugs, configures, and optimizes serverless applications on AWS using Lambda, API Gateway, Step Functions, EventBridge, and SAM/CDK. Covers cold starts, CORS debugging, event source mappings, troubleshooting, concurrency, SnapStart, Powertools, function URLs, EventBridge Scheduler, Lambda layers, Durable Functions, durable execution, checkpoint-and-replay, and production readiness. Use when the user mentions Lambda, API Gateway, Step Functions, SAM templates, CDK serverless stacks, DynamoDB stream triggers, SQS event sources, cold starts, timeouts, 502/504 errors, throttling, concurrency, CORS, Powertools, Durable Functions, durable execution, checkpoint-and-replay, or any event-driven architecture on AWS, even if they don't say "serverless." Do NOT use for EC2, ECS/Fargate containers, or Amplify hosting.
Deploy an event-driven workflow that routes S3 uploads to either Lambda or Fargate via Step Functions based on file size. Uses EventBridge to trigger a Step Functions state machine when objects are uploaded to S3. Small files are processed by Lambda, large files by a Fargate task. Includes VPC, ECR repository, ECS cluster, and scoped IAM roles. Trigger keywords: Step Functions, Fargate, Lambda, S3 event, EventBridge, ECS, ECR, file processing, workflow orchestration, serverless.
DataWorks Infrastructure Management: Create and query operations for Data Sources (51 types), Compute Resources, and Serverless Resource Groups, plus connectivity testing and resource group binding/unbinding. Uses aliyun CLI to call dataworks-public OpenAPI (2024-05-18). Trigger keywords: DataWorks data source, compute resource, resource group, datasource, data source, compute resource, resource group, mysql/hologres/maxcompute data source, holo/mc/flink resource, Serverless resource group, DataWorks infra, create/list datasource, DW environment config, infrastructure initialization, connect database to DataWorks, database connection failure, configure holo/mc resource. Not triggered: data development tasks, scheduling configuration, MaxCompute table management, data integration tasks, ECS/RDS/OSS operations, workspace member management, data quality monitoring, data lineage, data preview.
Generate Harness v1 simplified Pipeline YAML using the new concise syntax with flat structure, ${{ }} expressions, script field, and action steps. Supports CI stages (run, run-test, background), CD stages (service/environment with action steps for K8s, Helm, ECS), approval (stage-level and inline), parallel execution, matrix/for/while strategies, caching, volumes, and templates. Use when asked for a v1 pipeline, simplified pipeline, new pipeline format, or when user specifically requests v1 syntax. Do NOT use for v0/standard pipelines (use create-pipeline). Trigger phrases: v1 pipeline, simplified pipeline, new pipeline format, create v1, modern pipeline syntax.
This skill should be used when containerizing applications with Docker, creating Dockerfiles, docker-compose configurations, or deploying containers to various platforms. Ideal for Next.js, React, Node.js applications requiring containerization for development, production, or CI/CD pipelines. Use this skill when users need Docker configurations, multi-stage builds, container orchestration, or deployment to Kubernetes, ECS, Cloud Run, etc.
Provides connectivity, authentication, and troubleshooting guidance for Amazon RDS for SQL Server. Applicable when users ask about SSMS times out connecting from EC2, Cannot generate SSPI context with Windows auth, connect RDS SQL Server from Lambda with pymssql, auth_scheme shows NTLM instead of KERBEROS on ECS Fargate, SSM tunnel to RDS SQL Server from laptop, port 1433 security group, TrustServerCertificate=True for localhost tunnels, SPN MSSQLSvc, AWS Managed Microsoft AD, CNAME not RDS endpoint for Kerberos, tds_version='7.4', encryption='require', port-as-string for pymssql, Secrets Manager credential caching in Lambda, error 18456 login failed. Covers Python (pymssql, pyodbc), .NET (Microsoft.Data.SqlClient), Java (JDBC mssql-jdbc), Node.js (tedious), IAM auth via RDS Proxy, and VPC/ECS/EKS/Lambda deployment.
Configures CI/CD pipelines using AWS CodePipeline, CodeBuild, CodeDeploy, CodeConnections, and CodeArtifact. Covers CodePipeline V2 (triggers, variables, execution modes, cross-account), buildspec.yml (caching, VPC, Docker), CodeDeploy strategies (blue/green, canary, linear), CodeArtifact (private package registries, auth tokens, cross-account), and source connections (GitHub, GitLab, Bitbucket). Applies when CodePipeline, CodeBuild, CodeDeploy, CodeConnections, CodeArtifact, buildspec.yml, appspec.yml, or CI/CD pipeline orchestration is referenced. Does NOT cover: ECS Fargate services or task definitions (use aws-containers), CDK Pipelines or cdk deploy (use aws-cdk), sam deploy (use aws-serverless), Amplify deployments (use aws-amplify), or GitHub Actions/GitLab CI.