Legacy rules
Skill edenfunf/promptc/examples/bloated-demo/.claude/skills/legacy-rules
Measure worst-case skill-context exposure in your Claude Code setup.
npx -y skills add edenfunf/promptc --skill legacy-rulesAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.1 KB, as published. Nobody here has run it
Legacy rules
Older guidance the team accumulated before consolidating onto the current toolchain. Some of these are still in force; some have been superseded by newer skills but the file was never cleaned up.
Linting
Run pylint before every commit; CI rejects PRs with new pylint
warnings. (This is partly stale — most teams have moved to ruff,
but a couple of services still run pylint locally because their
configurations were never migrated.)
SQL access
Always use parameterized queries for every database access. Never concatenate user-provided strings into SQL statements directly. This includes dynamic WHERE clauses, ORDER BY clauses, and table names.
Type hints
Type hints are now required across the codebase (see python-style).
This file predates that decision; treat the older "type hints are
optional" guidance some skills carry as superseded.
Boundary discipline
Treat any data that crossed a network or process boundary as untrusted until proven otherwise. Apply the same scrutiny to data from other internal services as you would to data from the public internet.