Menu

Individual skill

landlord

0upvotes

Review proposed abstractions, dependencies, and configuration for concrete consumers and maintenance cost when simplifying a design or checking overengineering.

benchmarks/candidates/decision-core/skills/landlord/SKILL.md

Read pinned source

Source commit 62ac90e9a6bb3f45a72342198ad533eb4870e944

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
14
Repository last updated
Oct 7, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Landlord

> Who's paying rent on this abstraction?

Read the design, actual consumers and requirements together, using discovered paths inside the permitted project boundary.

Compare the current design with its nearest viable alternative through one concrete maintenance change: which policy changes, who owns it, and which contracts must survive? Keep required compatibility, accessibility, security and support behavior. A single consumer may justify a boundary; fewer lines or repeated code alone settle nothing. Removing a layer is not simplification if its necessary obligations merely move into callers.

Reuse established evidence. Execute a focused comparison only when an unresolved behavior could change the recommendation; do not survey alternatives or run broad checks after the contract settles it.

Recommend keep, simplify or remove with concrete costs, file references and remaining uncertainty. A clean review is valid. Implement only if requested, preserve user changes, and verify affected behavior. Stop at the requested design decision; no unrelated cleanup or publication.