Skills are designed to be simpler than other modules to ensure that it is easy to get started.
To create a skill you need to at minimum create a single python file in your repository with the
__init__.py name. For example the skill
hello has a single file called
Within this file should be a class with methods decorated with an opsdroid matcher function to let opsdroid know when to trigger the skill. Let's get started with an example.
from opsdroid.skill import Skill from opsdroid.matchers import match_regex class HelloSkill(Skill): @match_regex(r'hi') async def hello(self, message): await message.respond('Hey')
In this example we are importing the
match_regex decorator from the opsdroid matchers library. We are then using it to decorate a simple hello world function.
This decorator takes a regular expression to match against the message received from the connector. In this case we are checking to see if the message from the user is "hi".
For more information about the different decorators available in opsdroid see the matchers documentation.
If the message matches the regular expression then the decorated function is called. As arguments opsdroid will pass a pointer to itself along with a Message object containing information about the message from the user.
To ensure the bot is responsive the concurrency controls introduced in Python 3.5 are used. This means that all functions which will be executed should be defined as an
async function, and calls to functions which may require IO (like a connector or database) should be awaited with the
await keyword. For more information see asyncio and event loops.
In opsdroid when events are received the connector emits
Event objects which can be matched by skills and processed. The most common event is the
Message event but a number of other events are implemented including:
Note: Not all connectors support all event types. To find out which events a connector will emit you can access the
.events attribute of a connector.
Event class has the following attributes. Also depending on the matcher it may have parser specific properties too. See the matchers documentation for more details.
user: A string containing the username of the user who wrote the message.
target: A string normally containing the name of the room or chat channel the message was sent in.
connector: A pointer to the opsdroid connector object which received the message.
raw_event: The raw event received by the connector (may be
responded_to: A boolean (True/False) flag indicating if this event has already had its
respond(text): A method which responds to the received message using the same connector.
In addition to the base properties listed above, the
Message class has the following properties:
text: A string containing the message from the user.
For more information on the other types of events see the events documentation.
opsdroid has a memory class which can be used to persist data between different connectors (which run in different process forks) and between restarts of the application.
The data can be accessed via the
memory property of the
opsdroid pointer which is passed to the skill function. The
memory object has the following methods.
Returns an object from the memory for the key provided.
Stores the object provided for a specific key.
from opsdroid.skill import Skill from opsdroid.matchers import match_regex class RememberSkill(Skill): @match_regex(r'remember (.*)') async def remember(self, message): remember = message.regex.group(1) await self.opsdroid.memory.put("remember", remember) await message.respond("OK I'll remember that") @match_regex(r'remind me') async def remember(self, message): information = await self.opsdroid.memory.get("remember") await message.respond(information)
In the above example we have defined two skill functions. The first takes whatever the user says after the word "remember" and stores it in the database.
The second retrieves and prints out that text when the user says "remind me".
All initialisation that might be required for your skill can go to the
__init__ method, which takes
config as its arguments.
class MySkill(Skill): def __init__(self, opsdroid, config): super(MySkill, self).__init__(opsdroid, config) # do some setup stuff here
IMPORTANT Always remember to chain up to the
__init__ method of the
Skill class, or your skill won’t work!
It is possible to decorate your function with multiple matchers. There are a couple of reasons why you would want to do this.
You can schedule a skill to run periodically using the crontab matcher. This allows you to decorate your function with a crontab expression which will run your function at that interval.
You can use this in conjunction with other chat based matchers which would allow you to call the function on demand as well as on a schedule.
Creating public skills with good parser support
You may wish to write a skill which you make publicly available. You will not know which parsers the users of your skill will have enabled and therefore it would be best to support them all.
When a message from a chat client is parsed by opsdroid all skills matching that message are given a score ,either by the NLP API or locally by opsdroid. This score is how confident the NLP service and opsdroid are that the message matches the skill and only the highest scoring skill is executed.
This means that if you decorate a skill with both the
dialogflow matchers then users who don't use Dialogflow will get a simple
regex match. However users with Dialogflow configured will get matches on more flexible messages, but will not see duplicate responses where the regex also matched.
See the following official modules for examples:
If you need help or if you are unsure about something join our gitter channel and ask away! We are more than happy to help you.