PromptCrew is a workspace for building, organizing, running, sharing, and improving reusable AI capabilities across a team or company.

An AI capability is a reusable piece of AI work. It can be a prompt, a skill, or an agent, combined with the knowledge, variables, instructions, and metadata needed to use it well.

A prompt library stores prompts. PromptCrew manages the full lifecycle: find existing work, attach knowledge, build or refine, run, organize, share, govern, and reuse AI capabilities.

You can create prompts, skills, and agents. Prompts are usually runnable in chat or document workflows. Skills are repeatable functions used inside tools. Agents are more autonomous workflows that often need integrations, APIs, repositories, or external agent platforms.

No. PromptCrew can run prompts and chatbot-friendly workflows directly. Some skills and agents may need to be copied, downloaded, or handed off to another platform such as Cursor, Claude Code, ChatGPT, or another connected AI tool.

The Assistant helps you find existing capabilities, search knowledge, refine existing work, build new capabilities, and think through ideas with AI assistance.

PromptCrew is designed to help teams reuse trusted work before creating something new. If a strong match exists, the Assistant recommends it and explains why it fits.

The Assistant can help build a new prompt, skill, or agent from your request. It may ask clarifying questions if it needs more detail about the audience, output, platform, knowledge, or integrations.

It may recommend knowledge only when specific context is needed, such as a policy, SOP, data file, example, brand guide, customer notes, or setup instructions. It should not ask for broad company knowledge when focused knowledge is enough.

Yes. You can refine a capability before using it, clone it, adapt it to your needs, or build a new version when the existing option is not quite right.

The Library is where users find, preview, clone, edit, run, and organize reusable AI capabilities.

Depending on your permissions, you can find prompts, skills, agents, personal drafts, team capabilities, company-shared capabilities, and community-published capabilities.

Search should prioritize relevance to your query, then signals such as usage, fit, and availability to you.

If you own it or have permission, you can edit it directly. If not, you can clone or adapt it into your own workspace.

Cloning creates your own copy of a capability so you can customize it without changing the original.

Yes. You can preview the description, AI instructions, variables, attached knowledge, metadata, and recommended platform.

The Builder is where users create or edit capabilities, including the human description, AI instructions, variables, type, category, platform, model provider, performance/cost level, permissions, and attached knowledge.

The Description is the human-facing README: what the capability does, how to use it, and where to run it. AI Instructions are the instructions the model follows when the capability runs.

Variables are placeholders users fill in before running a capability, such as customer name, target audience, document type, role, or source text.

PromptCrew can capture capability type, category, tags, variables, recommended platform, model provider, performance/cost level, output type, permissions, projects, and attached knowledge.

Recommended Platform tells users where the capability should run. Examples include PromptCrew, ChatGPT, Claude, Cursor, Claude Code, VS Code, or another connected AI platform.

Yes. PromptCrew can help generate descriptions, variables, categories, tags, recommended platforms, and performance/cost recommendations.

Knowledge is supporting context that helps a capability perform better. It can include files, documents, examples, SOPs, policies, data, notes, setup instructions, or reference material.

Attach knowledge when the capability needs specific context to produce a good result. Examples include company policies, brand voice, customer notes, sales materials, research, resumes, or process documentation.

No. Capabilities work best with curated knowledge. Use the Assistant to identify the exact files, examples, policies, and notes needed for the job instead of overwhelming the model with everything.

Temporary knowledge is context added for the current workspace or session. It helps with the current task but may need to be saved if you want to reuse it later.

Saved knowledge is stored in your knowledge library or project so it can be reused across capabilities and workspaces.

Workspace exports should include the capability, workspace instructions, and attached knowledge where available so the work can move to another platform.

Execute Mode lets users run a capability with its attached knowledge and variables.

Chat Mode is best for conversational work, Q&A, drafting, analysis, summarization, and iterative responses.

Some skills and agents require integrations, APIs, repository access, external tools, or autonomous execution. PromptCrew can help package the workspace, but another platform may be the right runtime.

Run Anyway asks PromptCrew to adapt the capability into the best possible Chat or Creator result, even if it cannot perform external actions or run integrations.

PromptCrew can store and package connected-tool setup context, but actual execution depends on the connected platform and runtime.

PromptCrew should ask users to fill in required variables before execution. If text has already been entered, it should carry that forward where possible.

Creator Mode is best when the desired output is a document or artifact, such as a brief, SOP, checklist, report, plan, PRD, or draft that the user can edit.

Use Creator Mode when you want the result in an editable document window instead of only a chat response.

Yes. Creator Mode can use the capability instructions, variables, and attached knowledge to produce a more grounded artifact.

A workspace is the current working set of capabilities, knowledge, variables, and context used for a task.

A project organizes related capabilities and knowledge so a team can reuse them together.

Save a workspace as a project when multiple capabilities or knowledge files should be reused together.

Yes. Additional capabilities and knowledge can be added to an active project.

PromptCrew should clone the capability for you, include your relevant knowledge, and add the new copy to your workspace or project.

Community is where users can discover, share, clone, and adapt capabilities beyond their private workspace or team library.

Publish reusable capabilities that are helpful beyond one private team or account and do not include sensitive context unless intentionally shared.

Others should typically clone or adapt their own copy rather than editing your original, depending on permissions.

It can. Review attached context carefully before publishing. PromptCrew should clearly warn users when knowledge may be included.

Users with appropriate permissions should be able to unpublish or remove community content.

Teams allow organizations to manage users, permissions, shared capabilities, knowledge, and projects.

Roles may include owners, admins, members, and viewers depending on the account setup.

Yes. Capabilities can be private, team-shared, organization-shared, or community-published depending on permissions.

Yes. Capabilities remain private unless shared with a team, organization, project, group, or Community.

PromptCrew is designed around improving and managing reusable capabilities, including ownership-aware edits, cloning, and historical context where supported.

Yes. Account admins can view usage and remaining credits where supported by the plan.

Higher-performance models and longer tasks may use more credits. PromptCrew uses performance/cost recommendations to help avoid unnecessary spend.

Performance/Cost recommends whether the capability needs High, Medium, or Low intelligence. Simple tasks may use lower-cost models, while complex reasoning, strategy, or synthesis may need higher performance.

Execution workflows may allow users to override the model or intelligence level, depending on account settings.

PromptCrew organizes knowledge with account permissions, project access, and sharing controls so teams can manage who can access sensitive context.

Review the capability instructions, description, variables, attached files, and knowledge. Do not publish private, customer, confidential, or regulated information unless intended and approved.

Yes. PromptCrew helps teams standardize AI workflows, reuse approved capabilities, manage access, reduce duplicated work, and provide clearer guidance on where capabilities should run.

PromptCrew found a reusable match that may save time. You can use it, refine it, clone it, or build something new.

It may be a skill or agent that requires external tools, integrations, APIs, or platform-specific execution.

The capability needs specific inputs before it can produce a useful result.

The capability may need more specific knowledge, clearer variables, or a better description of the desired output.

Temporary knowledge may need to be saved or added to the correct project, capability, or workspace.

Workspace exports may include the capability, workspace instructions, and attached knowledge so the work can be moved to another platform.