smelloscope avatar

smelloscope

Official

@smelloscope

0Followers
|
2Public Repos
|
5Published Skills

Smello captures HTTP requests, pytest runs, logs, and exceptions from Python codebases into a local debugging dashboard, with docs and landing-page maintenance skills.

Skills Distribution
DomainDeveloper To...HTTP Request Debug.. (40%)Test & Exception D.. (25%)Python Codebase In.. (20%)Documentation & La.. (15%)

Agent Skills by smelloscope

Showing 5 vetted skills indexed across 1 GitHub repositories.

Frequently Asked Questions About smelloscope

FAQPage Schema
What tasks can I accomplish with Smello's skills?

You can debug captured HTTP requests, pytest executions, logs, and exceptions; trace which test or endpoint made a request; analyze response bodies; run scripts or test suites under Smello instrumentation; and maintain Smello's own docs, landing page icons, and screenshots.

Who is Smello designed for?

Python developers and QA engineers who need to inspect outgoing API calls, diagnose failed or parametrized pytest cases, and troubleshoot exceptions. It also supports gRPC calls from Google Cloud libraries, suiting backend engineers debugging distributed service traffic locally.

How do I start a Smello debugging session?

Run your script, test suite, or app with Smello instrumentation while a Smello server is running. Captured events appear in a local web dashboard; paste a URL like http://localhost:5110/#<uuid> and the skill extracts the UUID after the hash as the event ID.

What are the prerequisites for using Smello?

A running Smello server is required for debugging sessions. Setup uses pip, uv, or docker to integrate Smello into a Python codebase, and the debugging skill relies on the smello CLI, python3, and jq for inspecting captured traffic and events.

Can Smello help maintain its own documentation site?

Yes. Dedicated skills add or update integration guides, edit landing page copy, find and add technology logos to the 'Works With' section, and regenerate dashboard and Claude Code session screenshots after UI or demo content changes.