agentiveau/myagentive

Overview

This skill helps you understand, configure, and troubleshoot MyAgentive, an open-source personal AI agent for power users. It explains required and optional configuration, key file locations, onboarding steps, and common fixes so you can get the agent running and customized quickly. Use it to manage API keys, sessions, media handling, and integration points like Telegram and the web UI.

How this skill works

I inspect configuration values, file locations, and service integrations used by MyAgentive and explain how they affect runtime behavior. I guide you through the setup wizard, show where to add optional API keys, and walk through commands to view or reset config and the database. For troubleshooting, I map symptoms (bot unresponsive, web UI down, failing API) to targeted checks and remediation steps.

When to use it

• Setting up MyAgentive for the first time or rerunning the setup wizard
• Adding or rotating API keys for transcription, image generation, or voice services
• Troubleshooting Telegram bot or web interface connectivity issues
• Locating config, system prompt, media, or database files for backup or inspection
• Adjusting agent behavior by editing the system prompt or switching sessions

Best practices

• Keep ~/.myagentive/config under your control and back it up before making changes
• Store sensitive keys securely and avoid committing them to source control
• Edit ~/.myagentive/system_prompt.md to tune agent identity; restart to apply changes
• Validate config with the provided check_config script before running in production
• Reset the database only when necessary; the app recreates it on next run

Example use cases

• Onboarding: clone, bun install, run dev to trigger the first-run wizard and enter TELEGRAM_BOT_TOKEN, TELEGRAM_USER_ID, and WEB_PASSWORD
• Add Deepgram for transcription: create a key, append DEEPGRAM_API_KEY to ~/.myagentive/config, then restart
• Telegram troubleshooting: verify TELEGRAM_USER_ID is numeric, confirm bot token contains ':' and that you ran /start with the bot
• Web interface down: curl http://localhost:3847/health, check configured port (default 3847) and server logs
• Reset config: rm ~/.myagentive/config to trigger setup wizard on next launch