
Mlog Query
Query or inspect repository-linked log metadata through the api/git skill package when debugging commits or API/git workflows.
Overview
mlog-query is an agent skill for the Operate phase that supports log-related querying in api/git-backed agent workflows.
Install
npx skills add https://github.com/api/git --skill mlog-queryWhat is this skill?
- Published under the api/git skills.sh source as mlog-query
- Pairs with git-oriented agent workflows rather than generic chat
- Suited to agents that already use skills.sh api/git tooling
Adoption & trust: 1 installs on skills.sh; trending (+100% hot-view momentum).
What problem does it solve?
You need a catalogued git/API skill hook for log queries instead of ad-hoc scripts every time an agent investigates repo or API history.
Who is it for?
Developers already using api/git skills who want a dedicated slug for log-query steps in agent playbooks.
Skip if: Teams without git-based workflows or anyone who needs full observability stacks (APM, centralized logging) rather than a git-package skill stub.
When should I use this skill?
When your agent workflow already uses api/git skills and you need a dedicated mlog-query step for log or history inspection.
What do I get? / Deliverables
Your agent can invoke mlog-query as a named step in a git-centric debugging or monitoring routine once the local SKILL.md documents the exact commands.
- Log or history query results as defined by the installed SKILL.md
Recommended Skills
Journey fit
Log and history lookup is most natural once code is in git and you are diagnosing production or CI issues in the Operate phase. Monitoring subphase fits tracing what changed in repos and correlating events with git history.
How it compares
Use as a focused skills.sh git utility, not as a replacement for hosted log platforms or MCP log servers.
Common Questions / FAQ
Who is mlog-query for?
Solo and indie builders who install skills from the api/git source and want a named log-query capability for coding agents.
When should I use mlog-query?
During Operate monitoring when you are tracing issues alongside git history, or in Build integrations when wiring agents to api/git tooling—after you verify what the installed skill actually runs.
Is mlog-query safe to install?
Review the Security Audits panel on this Prism page and read the skill source; listing metadata alone does not document permissions or network access.
SKILL.md
READMESKILL.md - Mlog Query
# mlog-query Installs: 1 Source: api/git { "url": "https://www.skills.sh/site/api.git/mlog-query", "name": "mlog-query", "rank": 2247, "slug": "mlog-query", "change": 1, "source": "api/git", "installs": 1, "skillsShId": "api/git/mlog-query", "sourceType": "well-known", "installsYesterday": 0 }