Inventory the APIs other modules consume, to choose package-split extraction boundaries.
75%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.agents/skills/package-split/SKILL.mdRun from the repository root; --help lists options. Both commands are static, over-approximating
inventories, not compatibility proofs, and always exit 0 on success (2 on usage or input errors).
Files the interpreter cannot parse are skipped and listed on stderr and in the JSON unparsed field.
scripts/package-split api-usage --module ddtrace.internal.coverage [--source-path ddtrace ...]
scripts/package-split api-surface [--source-path ddtrace ...] [--zones <layers.json>] [--top 30]api-usage lists every symbol of the target consumed outside it, with call/subclass/raise/except/read context.
Run it over production code first, then use --source-path ddtrace --source-path tests for a combined inventory.
For a test-only scan, use --source-path tests --allow-absent-target; re-export attribution then depends on facades present in that scope.api-surface groups consumed symbols by owning module and zone (default:
scripts/import-analysis/layers.json), and suggests modules whose consumers all live in one zone..package-split/<command>/<scope>/; api-usage also nests it under the target module. The command prints the exact path (--output changes the root).Use the results to propose a narrow supported API for the extraction and get scope and naming
approved before moving code. Report the commands run, the proposed surface, and usages you chose
not to support. Add fixtures for new analysis cases in tests/package_split/, then use
scripts/run-tests and scripts/lint.
DataDog/dd-trace-py
ac91ade
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.