Skip to main content
All CollectionsDeveloping Actors
How to write great README for your actors
How to write great README for your actors

Learn how to write an effective README for your actor and get started using our template.

Kirill Turin avatar
Written by Kirill Turin
Updated over a week ago

Writing a README can be difficult for developers, especially after spending a long time developing their actor. However, it is the first page users will see when they try to use your actor. Its job is to attract the users' attention and describe to them what the actor does and how to use it. Thus, the complexity of the README should match the complexity of the actor. The following article provides an example of how to write a README for your actor. 

The README is written in the file in your actor's repository. From there, it is automatically fetched during the build process.


  • Introduction

  • Use Cases

  • Input

  • Output

  • Miscellaneous

First things first: to make your actor easy to find, don't forget to word your actor's title as we describe in the SEO for Actors article. Be sure to also use these principles in your actor's description and throughout the file. You don't need to repeat your actor's README in the description - instead use it to provide a brief, search engine friendly summary. 

A detailed TEXT description of what your actor can do and why you developed it. 

Use cases
LIST typical scenarios in which your actor can be useful. Include information on how exactly your actor can be used in these cases.

LIST all possible inputs for your actor. Do not go into the complete technical description - you can explain this in your actor's Input Schema.

CODE example of one of your results in JSON format. For brevity, only provide a snapshot of the actor's output. For real-time examples, add a Public run ID in your actor's Publication tab.

A short TEXT summary including some specific notes on your actor. Additionally, include links to tutorials and other relevant sources.

A few examples

Did this answer your question?