Sentry Miniapp SDK
lizhiyao/sentry-miniapp
Full Sentry SDK setup for Mini Programs — error monitoring, tracing, offline cache, source maps.
A skill your agent uses when implementing logging, error tracking, or monitoring in Frappe v14-v16.
Install Frappe Core Logging
$ npx skills add Impertio-Studio/Frappe_Claude_Skill_Package --skill frappe-core-logging -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Impertio-Studio/Frappe_Claude_Skill_Package frappe-core-logging --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Impertio-Studio/Frappe_Claude_Skill_Package.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/source/core/frappe-core-logging .claude/skills/frappe-core-logging && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "frappe-core-logging" agent skill from https://github.com/Impertio-Studio/Frappe_Claude_Skill_Package/tree/main/skills/source/core/frappe-core-logging into .claude/skills/frappe-core-logging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frappe-core-logging", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Impertio-Studio/Frappe_Claude_Skill_Package/tree/main/skills/source/core/frappe-core-loggingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Impertio-Studio/Frappe_Claude_Skill_Package --skill frappe-core-logging -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Impertio-Studio/Frappe_Claude_Skill_Package frappe-core-logging --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Impertio-Studio/Frappe_Claude_Skill_Package.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/source/core/frappe-core-logging .agents/skills/frappe-core-logging && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "frappe-core-logging" agent skill from https://github.com/Impertio-Studio/Frappe_Claude_Skill_Package/tree/main/skills/source/core/frappe-core-logging into .agents/skills/frappe-core-logging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frappe-core-logging", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Impertio-Studio/Frappe_Claude_Skill_Package --skill frappe-core-logging -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Impertio-Studio/Frappe_Claude_Skill_Package frappe-core-logging --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Impertio-Studio/Frappe_Claude_Skill_Package.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/source/core/frappe-core-logging .cursor/skills/frappe-core-logging && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "frappe-core-logging" agent skill from https://github.com/Impertio-Studio/Frappe_Claude_Skill_Package/tree/main/skills/source/core/frappe-core-logging into .cursor/skills/frappe-core-logging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frappe-core-logging", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Impertio-Studio/Frappe_Claude_Skill_Package.git --path skills/source/core/frappe-core-logging--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Impertio-Studio/Frappe_Claude_Skill_Package --skill frappe-core-logging -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Impertio-Studio/Frappe_Claude_Skill_Package frappe-core-logging --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Impertio-Studio/Frappe_Claude_Skill_Package.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/source/core/frappe-core-logging .gemini/skills/frappe-core-logging && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "frappe-core-logging" agent skill from https://github.com/Impertio-Studio/Frappe_Claude_Skill_Package/tree/main/skills/source/core/frappe-core-logging into .gemini/skills/frappe-core-logging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frappe-core-logging", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Impertio-Studio/Frappe_Claude_Skill_Package frappe-core-loggingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Impertio-Studio/Frappe_Claude_Skill_Package --skill frappe-core-logging -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Impertio-Studio/Frappe_Claude_Skill_Package.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/source/core/frappe-core-logging .github/skills/frappe-core-logging && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "frappe-core-logging" agent skill from https://github.com/Impertio-Studio/Frappe_Claude_Skill_Package/tree/main/skills/source/core/frappe-core-logging into .github/skills/frappe-core-logging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frappe-core-logging", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Impertio-Studio/Frappe_Claude_Skill_Package --skill frappe-core-logging -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Impertio-Studio/Frappe_Claude_Skill_Package frappe-core-logging --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Impertio-Studio/Frappe_Claude_Skill_Package.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/source/core/frappe-core-logging .opencode/skills/frappe-core-logging && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "frappe-core-logging" agent skill from https://github.com/Impertio-Studio/Frappe_Claude_Skill_Package/tree/main/skills/source/core/frappe-core-logging into .opencode/skills/frappe-core-logging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frappe-core-logging", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
frappe-core-logging- GitHub stars
- 188
- Token cost
- ~1.7k tokens
- SKILL.md length
- 333 words
- Files
- 3 (incl. references)
- Skills in repo
- 61
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when implementing logging, error tracking, or monitoring in Frappe v14-v16.
- Implementing logging
- SKILL.md covers Three Logging Mechanisms, Decision Tree, Quick Reference: frappe.logger() and Quick Reference:…, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Monitoring in Frappe v14-v16
What it does
Frappe Core Logging is an agent skill from Impertio-Studio/Frappe_Claude_Skill_Package. Use when implementing logging, error tracking, or monitoring in Frappe v14-v16. Covers frappe.logger() for file-based logging, frappe.logerror() for Error Log DocType entries, request logging, Sentry integration, and production logging patterns. Prevents common mistakes with print(), swapped logerror arguments, and sensitive data. Keywords: frappe.logger, logerror, Error Log, logging, Sentry,, where are the logs, how to log errors, error tracking, print not showing, production logs. monitor, request logging…
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/error-tracking.md` and `references/logger-patterns.md`). Compatibility notes: Claude Code, Claude.ai Projects, Claude API. Frappe v14-v16.
It sits in DevOps & Cloud. It works with Sentry. The repository describes itself as: 60 deterministic Claude AI skills for Frappe Framework & ERPNext v14-v16 development and operations. The licence is MIT.
When your agent uses it
- Implementing logging
- Monitoring in Frappe v14-v16
Example prompts
- “/frappe-core-logging”
Requirements
- Python 3
- Compatibility (from SKILL.md): Claude Code, Claude.ai Projects, Claude API. Frappe v14-v16.
What it can do on your machine
Read from SKILL.md and the folder at commit 36cfa80. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are python).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Claude Code, Claude.ai Projects, Claude API. Frappe v14-v16.
From compatibility in the SKILL.md frontmatter.
Context cost
Frappe Core Logging loads about 1.7k tokens when it runs, and up to ~4.2k if it reads all its reference files. Until then it costs about 143 tokens; SKILL.md has 333 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Impertio-Studio/Frappe_Claude_Skill_Package at commit 36cfa80, republished under its MIT licence (© Impertio-Studio). 333 words, ~1,715 tokens.
Download SKILL.mdSave it as
.claude/skills/frappe-core-logging/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- frappe-core-logging
- description
- Use when implementing logging, error tracking, or monitoring in Frappe v14-v16. Covers frappe.logger() for file-based logging, frappe.log_error() for Error Log DocType entries, request logging, Sentry integration, and production logging patterns. Prevents common mistakes with print(), swapped log_error arguments, and sensitive data. Keywords: frappe.logger, log_error, Error Log, logging, Sentry,, where are the logs, how to log errors, error tracking, print not showing, production logs. monitor, request logging, error tracking, debug, production.
- compatibility
- Claude Code, Claude.ai Projects, Claude API. Frappe v14-v16.
- license
- MIT
- metadata.author
- OpenAEC-Foundation
- metadata.version
- 3.0
Frappe Logging & Error Tracking
Three Logging Mechanisms
| Mechanism | Storage | Use For |
|---|---|---|
frappe.logger() | File (rotating) | Application logging, debug info, audit trails |
frappe.log_error() | Database (Error Log DocType) | Errors visible in admin UI, persistent tracking |
frappe.log() / frappe.errprint() | stderr / request-scoped | Quick debugging only (NOT for production) |
Decision Tree
Need to log something?
│
├─ Application logging (info, debug, warnings)?
│ └─ frappe.logger("my_module").info("message")
│ → Writes to sites/{site}/logs/my_module.log
│
├─ Error that admins should see in Desk UI?
│ └─ frappe.log_error(title="Short desc", message=traceback)
│ → Creates Error Log document (queryable, auto-cleanup)
│
├─ Quick debug during development?
│ └─ frappe.errprint(variable) — shows in console
│ → NEVER leave in production code
│
├─ Track all HTTP requests?
│ └─ Set enable_frappe_logger: true in site_config.json
│ → Logs to frappe.web.log
│
├─ Performance monitoring?
│ └─ Set monitor: true in site_config.json
│ → Logs to monitor.json.log (JSON, per-request metrics)
│
└─ External error tracking (Sentry)?
└─ Set FRAPPE_SENTRY_DSN environment variable
→ Auto-captures unhandled exceptionsQuick Reference: frappe.logger()
# Get a logger for your module (ALWAYS specify module name)
logger = frappe.logger("my_app")
# Standard Python logging levels
logger.debug("Detailed diagnostic info")
logger.info("Normal operations: processed 50 records")
logger.warning("Something unexpected but recoverable")
logger.error("Operation failed", exc_info=True)
logger.critical("System-level failure")
# Full signature
frappe.logger(
module=None, # Logger name + log filename
with_more_info=False, # Auto-log request form_dict
allow_site=True, # Log under site's logs/ directory
filter=None, # Custom logging.Filter
max_size=100_000, # Max bytes per log file (100KB default)
file_count=20 # Rotated files retained (20 default)
)Log location: sites/{site}/logs/{module}.log
Rotation: RotatingFileHandler — 100KB per file, 20 backups (~2MB total per logger)
Default Log Levels
| Mode | Level | Effect |
|---|---|---|
Development (_dev_server) | WARNING | Debug/info suppressed |
| Production | ERROR | Only errors and above |
# Change level dynamically
frappe.utils.logger.set_log_level("DEBUG")Quick Reference: frappe.log_error()
# ALWAYS use keyword arguments (title/message can swap otherwise)
frappe.log_error(
title="Payment gateway timeout", # Short description (140 chars max)
message=frappe.get_traceback(), # Full error details
reference_doctype="Payment Entry", # Related DocType
reference_name="PE-00001" # Related document
)
# Minimal — auto-captures current traceback
try:
risky_operation()
except Exception:
frappe.log_error(title="Operation failed")Error Log cleanup: Auto-deletes after 30 days. Manual: frappe.whitelist: clear_error_logs()
Auto-Captured Exceptions
Unhandled exceptions (HTTP 500+) are automatically logged to Error Log.
Excluded from auto-capture:
frappe.AuthenticationErrorfrappe.CSRFTokenErrorfrappe.SecurityExceptionfrappe.InReadOnlyMode
Production Configuration
site_config.json Keys
| Key | Value | Effect |
|---|---|---|
enable_frappe_logger | true | HTTP request logging → frappe.web.log |
logging | 2 | Log all SQL queries (debug only!) |
monitor | true | Request/job metrics → monitor.json.log |
disable_error_snapshot | true | Disable auto-capture of exceptions |
Environment Variables
| Variable | Effect |
|---|---|
FRAPPE_STREAM_LOGGING=1 | Log to stderr instead of files |
FRAPPE_SENTRY_DSN=<dsn> | Enable Sentry error tracking |
ENABLE_SENTRY_DB_MONITORING | Track SQL queries in Sentry |
SENTRY_TRACING_SAMPLE_RATE | Performance tracing rate (0.0-1.0) |
Production Log Files
| File | Content |
|---|---|
logs/web.error.log | HTTP errors (supervisor) |
logs/web.log | Gunicorn stdout |
logs/worker.error.log | Background job errors |
logs/frappe.log | Default frappe logger |
logs/frappe.web.log | HTTP request metadata |
logs/monitor.json.log | Performance metrics (JSON) |
sites/{site}/logs/*.log | Per-site application logs |
Anti-Patterns
| NEVER | ALWAYS | Why |
|---|---|---|
print("debug info") | frappe.logger("mod").info(...) | print() disappears in production |
frappe.log_error("info msg") | frappe.logger().info(...) | log_error creates Error Log docs, clutters admin UI |
frappe.logger() (no module) | frappe.logger("my_module") | No-module mixes with framework logs |
frappe.log_error(title, msg) positional | frappe.log_error(title=t, message=m) | Positional args can swap (known quirk) |
| Log passwords/tokens | Mask sensitive data | SiteContextFilter only masks form_dict |
frappe.log() in production | frappe.logger() | frappe.log() is debug-only, request-scoped |
Leave logging=2 in prod | Only during debugging | Logs ALL SQL queries, massive I/O |
Version Differences
| Feature | v14 | v15+ |
|---|---|---|
frappe.logger() | Yes | Yes |
frappe.log_error() | Yes | + defer_insert kwarg |
| Error Log trace_id | -- | Added |
| Error Log metadata | -- | JSON request/job context |
| Error snapshots | File-based + scheduled collection | Direct DB insert |
| Sentry integration | Basic | Enhanced (DB monitoring, profiling) |
guess_exception_source() | -- | Identifies which app caused error |
FRAPPE_STREAM_LOGGING | Yes | Yes |
Reference Files
- Logger API & Patterns — frappe.logger() advanced usage
- Error Tracking — Error Log, Sentry, monitoring
© Impertio-Studio, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (references) in skills/source/core/frappe-core-logging of Impertio-Studio/Frappe_Claude_Skill_Package.
- SKILL.md
- references/error-tracking.md
- references/logger-patterns.md
Open the folder on GitHubat commit 36cfa80
Compare with similar skills
Frappe Core Logging next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Frappe Core Logging this skillImpertio-Studio/Frappe_Claude_Skill_Package | 188 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Sentry Miniapp SDKlizhiyao/sentry-miniapp | 687 | — | ~5.1k | Automated safety check: Pass | MIT | |
| Logging Observabilitygetsentry/toolkit | 918 | — | ~2.6k | Automated safety check: Pass | Custom licence | |
| Temps Best Practicesgotempsh/temps | 828 | — | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| Axiom SRE Investigatoropenclaw/clawhub | 9.5k | — | ~7.1k | Automated safety check: Pass | MIT | |
| Cross Source Correlationaozyildirim/Agena | 102 | — | ~756 | Automated safety check: Pass | MIT |
Similar skills
- Official
Logging Observability
getsentry/toolkit
Review code for correct logging and error handling patterns.
Temps Best Practices
gotempsh/temps
Best-practices reference for preparing and instrumenting applications on Temps.
Axiom SRE Investigator
openclaw/clawhub
Investigates incidents and production problems with hypothesis-driven debugging, queries Axiom observability data when available, and keeps secrets out of commands and output.
Cross Source Correlation
aozyildirim/Agena
Correlate near-in-time events across PR merges, deploys, monitoring (Sentry/NewRelic/Datadog/AppDynamics) and ticket trackers (Jira/Azure DevOps) into confidence-scored clusters that answer "which…
Superset Incident Triage
superset-sh/superset
Does a read-only first pass on a possible production incident: gathers deploy, Sentry and health-check signals, proposes a severity and status message, then stops for human approval.
More from Impertio-Studio/Frappe_Claude_Skill_Package
All 61 skills in this repoFrappe Ops Website Deploy
Impertio-Studio/Frappe_Claude_Skill_Package
Deploy HTML/CSS websites to ERPNext/Frappe (v15/v16) as Web Pages via the REST API.
Frappe Agent Architect
Impertio-Studio/Frappe_Claude_Skill_Package
A skill your agent uses when designing multi-app Frappe architectures, deciding whether to split functionality into separate apps, or implementing cross-app communication patterns.
Frappe Agent Debugger
Impertio-Studio/Frappe_Claude_Skill_Package
A skill your agent uses when debugging Frappe errors, using bench console for live inspection, analyzing tracebacks, or reading Frappe log files.
Frappe Agent Interpreter
Impertio-Studio/Frappe_Claude_Skill_Package
A skill your agent uses when receiving vague or unclear ERPNext/Frappe development requests that need interpretation.
Frappe Agent Migrator
Impertio-Studio/Frappe_Claude_Skill_Package
A skill your agent uses when migrating a Frappe app between major versions, detecting breaking API changes, or resolving post-migration errors.
Frappe Agent Validator
Impertio-Studio/Frappe_Claude_Skill_Package
A skill your agent uses when reviewing or validating Frappe/ERPNext code against best practices and common pitfalls.
Related
Works with
Categories
Questions about Frappe Core Logging
What does Frappe Core Logging do?
A skill your agent uses when implementing logging, error tracking, or monitoring in Frappe v14-v16. Frappe Core Logging is an agent skill from Impertio-Studio/Frappe_Claude_Skill_Package. Use when implementing logging, error tracking, or monitoring in Frappe v14-v16.
When should I use Frappe Core Logging?
Frappe Core Logging fits situations like: implementing logging; monitoring in Frappe v14-v16.
How do I install Frappe Core Logging in Claude Code?
Run `npx skills add Impertio-Studio/Frappe_Claude_Skill_Package --skill frappe-core-logging -a claude-code`. Or copy the skill folder (skills/source/core/frappe-core-logging in Impertio-Studio/Frappe_Claude_Skill_Package) into .claude/skills/frappe-core-logging in your project. Claude Code loads it when a task matches its description.
How do I install Frappe Core Logging in Codex?
Run `npx skills add Impertio-Studio/Frappe_Claude_Skill_Package --skill frappe-core-logging -a codex`. Or copy the skill folder (skills/source/core/frappe-core-logging in Impertio-Studio/Frappe_Claude_Skill_Package) into .agents/skills/frappe-core-logging in your project. Codex loads it when a task matches its description.
Can I use Frappe Core Logging in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Impertio-Studio/Frappe_Claude_Skill_Package --skill frappe-core-logging -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/frappe-core-logging, .gemini/skills/frappe-core-logging, .github/skills/frappe-core-logging and .opencode/skills/frappe-core-logging in your project.
What does Frappe Core Logging need to run?
SKILL.md names no scripts, command-line tools or credentials: Frappe Core Logging is instructions for the agent only. Our summary lists: Python 3. Compatibility (from SKILL.md): Claude Code, Claude.ai Projects, Claude API. Frappe v14-v16..
Does Frappe Core Logging access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Frappe Core Logging safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Frappe Core Logging use?
Frappe Core Logging is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Frappe Core Logging use?
About 1.7k tokens (SKILL.md is roughly 6.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.5k tokens, read only when the agent opens those files.
What are the alternatives to Frappe Core Logging?
Skills that share tags, products or a category with Frappe Core Logging: Sentry Miniapp SDK (lizhiyao/sentry-miniapp, 687 stars), Logging Observability (getsentry/toolkit, 918 stars), Temps Best Practices (gotempsh/temps, 828 stars) and Axiom SRE Investigator (openclaw/clawhub, 9.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Frappe Core Logging?
Impertio-Studio (a GitHub organization) maintains it in Impertio-Studio/Frappe_Claude_Skill_Package, which has 188 GitHub stars. The repository holds 61 skills in this directory. The repository was last updated on September 17, 2026.
Source: Impertio-Studio/Frappe_Claude_Skill_Package on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.