Self-Evolving Skill: This skill improves through use. If instructions are wrong, parameters drifted, or a workaround was needed — fix this file immediately, don't defer. Only update for real, reproducible issues.
Automate repetitive workflows and reduce manual effort
Example: Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example: Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example: Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Time estimate: 15-45 minutes depending on use case complexity
Prerequisites
Submit your Claude Code skill and start earning
epx add terrylica/cc-skills --skill python-logging-best-practicesCompatible with
Supported agents
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionpython-logging-best-practicesExecute the skills CLI command in your project's root directory to begin installation:
epx add terrylica/cc-skills --skill python-logging-best-practicesFetches python-logging-best-practices from terrylica/cc-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
.cursor/skills/python-logging-best-practices
Restart Cursor to activate python-logging-best-practices. Access via /python-logging-best-practicesin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
python-expert-best-practices-code-review
wispbit-ai/skills · Backend · 3 shared tags
typescript-best-practices
jwynia/agent-skills · Backend · 2 shared tags
godot-best-practices
jwynia/agent-skills · Backend · 2 shared tags
nestjs-best-practices
kadajett/agent-nestjs-skills · Productivity · 2 shared tags
svelte5-best-practices
ejirocodes/agent-skills · Frontend · 2 shared tags
tanstack-query-best-practices
deckardger/tanstack-agent-skills · Productivity · 2 shared tags
Useful defaults in python-logging-best-practices — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
python-logging-best-practices has been reliable in day-to-day use. Documentation quality is above average for community skills.
Registry listing for python-logging-best-practices matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: python-logging-best-practices is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend python-logging-best-practices for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Registry listing for python-logging-best-practices matched our evaluation — installs cleanly and behaves as described in the markdown.
python-logging-best-practices fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
python-logging-best-practices is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Registry listing for python-logging-best-practices matched our evaluation — installs cleanly and behaves as described in the markdown.
python-logging-best-practices reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 46