openclaw - 💡(How to fix) Fix [Bug]: cannot call a second skill in one session [7 comments, 3 participants]

Fix Plan

The issue seems to be related to the skill configuration or the routing chain. To fix this, we need to ensure that the skills are properly configured and the routing chain is correctly set up.

Here are the steps to fix the issue:

• Check the skill configuration to ensure that the skills are correctly defined and enabled.
• Verify that the routing chain is correctly set up to call the expected skills based on the messages sent to the session.
• Update the code to handle the case where a skill is not found, to provide a more informative error message.

Example code snippet to handle the case where a skill is not found:

try:
    # Call the skill
    skill = get_skill(skill_name)
    skill.execute()
except SkillNotFoundError:
    # Handle the case where the skill is not found
    error_message = f"Tool {skill_name} was not found. Please check the skill configuration."
    print(error_message)

In the above code, we are catching the SkillNotFoundError exception and providing a more informative error message.

Verification

To verify that the fix worked, follow these steps:

• Open a new session and send a message to trigger the first skill.
• Send another message to trigger the second skill.
• Verify that both skills are called correctly and the expected output is displayed.

Extra Tips

• Make sure to check the skill configuration and routing chain setup to ensure that they are correct.
• Use logging to debug the issue and provide more informative error messages.
• Consider adding a fallback mechanism to handle cases where a skill is not found, to provide a better user experience.