AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Prompting Company

skill-promptingcompany-agent-skills-prompting-company · by promptingcompany

>

↗ Repository
— No reviews yet
0 installs
5 views
0.0% view→install

Install

$ agentstack add skill-promptingcompany-agent-skills-prompting-company

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Prompting Company? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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?"

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.

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

Workflows

1. Live Documentation Lookup

See [workflows/live-docs.md](workflows/live-docs.md) for source-of-truth URLs. Summary:

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

2. Entrypoint Selection

See [workflows/entrypoints.md](workflows/entrypoints.md) for full steps. Summary:

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

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.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Agent Skills