Recommended Reading: Use Case Best Practices
Creating a Use Case for the First Time
OpenAI Hub.
Select Submit a Use Case.
Here, you can determine which Use Case Extraction path is best for you:
How to Extract Use Cases
Paste Text: Best for a raw transcript or a messy document. Pragmatico will fill in the blanks to build the skill for you; you can always edit the rest!
Paste text for a prompt or transcript you already used.
Upload a document for a .txt, .docx, or .pdf file up to 20MB. Pragmatico will fill in the blanks to build the skill for you; you can always edit the rest!
Upload a skill for a .md or .skill file. Pragmatico will fill in the necessary information to populate the use case for you to share it with your colleagues. The skill stays as you uploaded it.
Want total control end to end?
Build it yourself to open a blank form.
Processing can take up to a couple of minutes depending on how large of a file was uploaded.
If you submit while the use case is still being prepared, you'll see "Preparing your use case," then "Submitting..." It submits once that finishes. Save draft does not start that wait.
Best Practices on Submitting Use Cases
Read the inferred title, description, and skill before you submit. Change anything that does not match the work.
Fill in Name and Skill. Submit stays unavailable until you fill in both.
Add Description, About, and Tips on how to use this when you have them.
Under Features, select any that apply: Prompt, Skill, Deep Research, File Upload, Agent.
Under Access, choose who can see this use case?: My Company, Specific departments, or Just me. Specific departments need at least one department.
Select Save draft to keep working, or Submit for review when the name and skill are ready.
A skill file is kept as you uploaded it. Pasted documents are turned into fields for you to review.
For Employees | What is a Use Case? explains who can see the use case.
What happens next
The note under the form tells you which path your organization uses:
If your organization reviews new use cases, you see Submitted for review. You get a notification when it is approved or sent back.
If it publishes straight away, you see Published to your library.
If it was not accepted, you see Sent back by your moderators. That draft cannot be resubmitted. Start a new one if you want to try again.
How your Org manages AI Use Case Publishing is in For Admins | How to Curate your AI Hub.
To change a use case that is already live, open it and select Propose a change. Those steps are in For Employees | What is a Use Case?
Who Can See Your Use Cases
The Access choice on the draft and in the editor determines who can see a use case:
My Company reaches everyone at your organization. This is the default and recommended!
Specific departments reach only the departments you tick. Choose at least one department, or share it company-wide.
Just me reaches you as the author. Only you can find and use it.
That choice controls who can find the use case, open it, and download its skill. It doesn't decide who can submit new use cases or who reviews them.
Submitting a change to a use case that is already live
Use Case Versioning lets co-workers improve use cases once they are live. Pragmatico encourages all users to suggest changes to use cases when they find an improvement. A rising tide lifts all boats!
On any use case, select "Submit a Change" at the top right.
Now, you are creating a *new version* of the existing use case. It cannot go live until your Moderator has approved the Use Case.
Open the use case in AI Hub and select Propose a change.
The heading is the use case name, or Untitled use case if it has no name. The Revision card says New submission, or Editing vN · current when a version already exists.
On the left, change Name, One-line description, Description, Skill, and Run tips as needed.
On the right, set Use case visibility, read the Revision card, pick Features, and under Details change Category, Scope, Level, and Tags.
Select Submit a New Version, or Publish Use Case if you can publish. If nothing changed, the button stays disabled and the card shows Nothing to submit or Nothing to publish. Cancel leaves without submitting.
A proposed change waits for a moderator. Nothing on the live page changes until they approve it, and only one change can be waiting at a time.
If you can publish, confirm the names who the new version will be live for, and select Publish.
Common Questions
Why is a saved Use Case no longer available?
A use case you saved can leave Saved when you no longer have access to it.
On the Saved tab, you will see a note that a use case you saved is no longer available because access has changed.
Why did I get an email saying that a use case is live?
A moderator approved a use case you submitted. It is now published in your organization's AI Hub.
The subject includes the use case name and "is now live in the AI Hub." The email names the approver, the organization it is in, and who can see it. Select View in AI Hub to open it.
You receive this only when someone else approves your submission. You do not get it if you approved your own work, if your organization publishes new use cases without review, or if an admin republishes an edit of a use case that is already live. If your account is deactivated, we don't send the email.
Why was a Use Case sent back by email?
A moderator reviewed a use case you submitted and sent it back. It has not been published.
The subject includes the use case name and "was sent back for changes." The email names the reviewer and the reason under Why it came back. Select Open your use case to see that draft.
What if the file is rejected when I create a Use Case?
If the file is the wrong type, you see Skill files must be Markdown (.md or .skill) or Upload a .txt, .docx, or .pdf file. If processing cannot use that input, you see Nothing usable was found, or We couldn't process this. Select Try a different input.