appfolio-common-errors
A diagnostic tool for AppFolio Stack API integrations, specifically covering HTTP errors and property-management-specific validation issues.
Install
mkdir -p .claude/skills/appfolio-common-errors && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/19499" && unzip -o skill.zip -d .claude/skills/appfolio-common-errors && rm skill.zipInstalls to .claude/skills/appfolio-common-errors
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Diagnose and fix common AppFolio API integration errors.Key capabilities
- →Diagnose HTTP-level API failures
- →Classify errors into auth, rate limit, validation, or server categories
- →Verify portfolio base URL configurations
- →Implement exponential backoff for rate limit recovery
- →Validate required fields for work orders and tenant creation
How it works
The skill provides a classification function to map HTTP status codes to specific error categories and offers a diagnostic curl command to verify connectivity.
Inputs & outputs
When to use appfolio-common-errors
- →Troubleshoot 404 tenant lookup failures
- →Verify portfolio base URL configurations
- →Resolve 409 lease conflict errors
- →Debug 401 unauthorized credential issues
About appfolio-common-errors
It provides a reference for debugging AppFolio API failures such as 401, 403, 404, 409, and 422 codes. It helps developers identify root causes like credential rotation, incorrect subdomains, or conflicting business logic.
Diagnose and fix common AppFolio API integration errors.
When not to use it
- →When the AppFolio platform status page indicates a known outage
- →When attempting to reuse unit IDs across different subdomains
Prerequisites
Limitations
- →Rate limits are enforced per API key, not per portfolio
- →Unit IDs are portfolio-specific and cannot be reused across subdomains
How it compares
Unlike generic debugging, this skill provides specific recovery patterns for property-management-specific validation errors and multi-portfolio base URL handling.
Compared to similar skills
appfolio-common-errors side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| appfolio-common-errors (this skill) | 0 | 3mo | Review | Intermediate |
| juicebox-common-errors | 1 | 3mo | Review | Beginner |
| fastapi-templates | 520 | 5mo | No flags | Intermediate |
| fastapi-pro | 79 | 6mo | No flags | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by jeremylongshore
View all by jeremylongshore →You might also like
juicebox-common-errors
jeremylongshore
Diagnose and fix Juicebox common errors. Use when encountering API errors, debugging integration issues, or troubleshooting Juicebox connection problems. Trigger with phrases like "juicebox error", "fix juicebox issue", "juicebox not working", "debug juicebox".
fastapi-templates
wshobson
Create production-ready FastAPI projects with async patterns, dependency injection, and comprehensive error handling. Use when building new FastAPI applications or setting up backend API projects.
fastapi-pro
sickn33
Build high-performance async APIs with FastAPI, SQLAlchemy 2.0, and Pydantic V2. Master microservices, WebSockets, and modern Python async patterns. Use PROACTIVELY for FastAPI development, async optimization, or API architecture.
sqlite-inspector
mikopbx
Проверка консистентности данных в SQLite баз данных MikoPBX после операций REST API. Использовать при валидации результатов API, отладке проблем с данными, проверке связей внешних ключей или инспектировании CDR записей для тестирования.
springboot-patterns
affaan-m
Spring Boot 架构模式、REST API 设计、分层服务、数据访问、缓存、异步处理和日志记录。适用于 Java Spring Boot 后端工作。
redis-inspect
civitai
Inspect Redis cache keys, values, and TTLs for debugging. Supports both main cache and system cache. Use for debugging cache issues, checking cached values, and monitoring cache state. Read-only by default.