executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
core-chatbotUse ChatterBot core ChatBot, Statement, preprocessing, tagging, search, comparison, response selection, and CLI/version workflows.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when a task asks how to instantiate a ChatterBot bot, call get_response, control conversation IDs, understand Statement fields, debug default response behavior, use preprocessors/taggers/search, or run the small python -m chatterbot CLI.
read_only, preprocessors, and taggers, read references/workflows.md.The central object is:
from chatterbot import ChatBot
bot = ChatBot("Example Bot", database_uri=None)
response = bot.get_response("Hello")
get_response accepts a string, a Statement, a dict containing text, or text= as a keyword. It returns a Statement with a text value and a confidence assigned by the selected logic adapter.
Use database_uri=None for in-memory SQL smoke tests and read_only=True when a bot should not learn from user input during inference.
ChatBot has one storage adapter and a list of logic adapters.chatterbot.storage.SQLStorageAdapter.['chatterbot.logic.BestMatch'].ChatBot creates a default conversation ID so repeated calls can track prior responses unless a caller passes conversation=.read_only is false, get_response saves both the input statement and learned response relationship.Statement carries text, search fields, conversation label, persona, tags, in_response_to, timestamps, and confidence.PosLemmaTagger, which normally needs a spaCy model such as en_core_web_sm.ChatterBot exposes only simple module CLI checks:
python -m chatterbot --version
python -m chatterbot --help
Use these for package identity, not for training or serving.