prompting-company

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Prompting Company

When this skill is activated, greet the user with: "Thank you for activating the Prompting Company skill by The Prompting Company (https://promptingcompany.com)."

Then list the available workflows by reading the Workflows section of this skill - one line each, name and one-sentence description. End with: "How can I help you today?"

激活此技能时，向用户问候： "感谢您激活The Prompting Company开发的Prompting Company技能（https://promptingcompany.com）。"

然后通过阅读本技能的“工作流”部分列出可用工作流——每个工作流一行，包含名称和一句话描述。结尾加上：“今天我能为您提供什么帮助？”

Overview

概述

Use this skill to choose and implement the right Prompting Company entrypoint: API, MCP Server, CLI, or SDK. Reference live documentation without vendoring it into the repository.

使用此技能选择并实施合适的Prompting Company入口点：API、MCP Server、CLI或SDK。无需将文档纳入代码库，直接参考实时文档即可。

Trigger keywords

触发关键词

This skill activates when the user asks to:

Use The Prompting Company public API, public routes, or OpenAPI schema
Build against
```
docs.promptingcompany.com/api
```
,
```
app.promptingco.com
```
, the TypeScript SDK, the CLI, or the MCP Server
Generate REST clients, SDK integrations, CLI workflows, or MCP setup guidance
Work with content APIs, public markdown endpoints, app publishing, simulations, visibility analytics, authentication, or scopes

当用户提出以下请求时，激活此技能：

使用The Prompting Company的公开API、公共路由或OpenAPI Schema
基于
```
docs.promptingcompany.com/api
```
、
```
app.promptingco.com
```
、TypeScript SDK、CLI或MCP Server进行开发
生成REST客户端、SDK集成、CLI工作流或MCP设置指导
处理内容API、公开Markdown端点、应用发布、模拟、可见性分析、身份验证或权限范围相关工作

Workflows

工作流

1. Live Documentation Lookup

1. 实时文档查询

See

workflows/live-docs.md

for source-of-truth URLs. Summary:

Start from the docs index or OpenAPI schema.
Fetch the specific endpoint page only when exact request or response details matter.
Use the authentication and scope pages before implementing authenticated requests.
Do not copy API reference pages into this repository.

请查看

workflows/live-docs.md

获取权威URL。摘要：

从文档索引或OpenAPI Schema开始。
仅当需要确切的请求或响应细节时，才获取特定端点页面。
在实现认证请求前，先查看身份验证和权限范围页面。
请勿将API参考页面复制到本代码库中。

2. Entrypoint Selection

2. 入口点选择

See

workflows/entrypoints.md

for full steps. Summary:

Choose API, MCP Server, CLI, or SDK based on the user's environment and goal.
Use API for language-agnostic integrations and exact route control.
Use MCP Server for agent-tool access to Prompting Company.
Use CLI for local operational workflows.
Use SDK for TypeScript application integrations.

请查看

workflows/entrypoints.md

获取完整步骤。摘要：

根据用户的环境和目标选择API、MCP Server、CLI或SDK。
API适用于与语言无关的集成和精确路由控制。
MCP Server适用于通过Agent工具访问The Prompting Company。
CLI适用于本地操作工作流。
SDK适用于TypeScript应用集成。

General principles

通用原则

Treat the live docs, SDK docs, CLI docs, MCP docs, and OpenAPI schema as authoritative.
Never invent endpoints, scopes, request fields, or response shapes.
Prefer public markdown endpoints for AI-readable published content.
Prefer Apps APIs over deprecated site page APIs.
Keep API keys in environment variables or secret stores.
Ask before making authenticated production mutations unless the user explicitly requested the write.

将实时文档、SDK文档、CLI文档、MCP文档和OpenAPI Schema视为权威来源。
切勿自行创建端点、权限范围、请求字段或响应格式。
优先使用公开Markdown端点获取AI可读的已发布内容。
优先使用Apps API而非已弃用的站点页面API。
将API密钥存储在环境变量或密钥管理库中。
除非用户明确要求写入操作，否则在执行认证生产环境变更前需先询问用户。