Install any skill in seconds. Free to start, no credit card required.
Get Started Free →datadrivenconstruction/security-review-construction
Security review checklist for construction software systems.
Passed 16 of 21 test cases with the skill, and 14 of 21 without it.
and 1 more in the full report
3 fixed14 passed either way4 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are building an automated bidding microservice for commercial construction tenders. Our team suggested logging full payload details including markup rates and subcontractor pricing to stdout during bid evaluation to assist with debugging. How should we configure logging and bid data handling for security?
| Checked | Without skill | With skill |
|---|---|---|
| The recommendations explicitly prohibit logging margin or markup details in application logs. | Passed | Passed |
| The recommendations require securing bid amounts until opening. | Missed | Passed |
The instructions your model reads when the skill loads.
This skill ensures all construction software systems follow security best practices, protecting sensitive project data, financial information, and business intelligence.
# CRITICAL: Construction financial data security
# ❌ NEVER Do This
project_budget = 15000000 # Hardcoded in source
margin_percentage = 0.18 # Business-sensitive info in code
# ✅ ALWAYS Do This
import os
from cryptography.fernet import Fernet
# Load from secure configuration
project_config = load_secure_config(os.environ['PROJECT_CONFIG_PATH'])
# Encrypt sensitive data at rest
def encrypt_financial_data(data: dict) -> bytes:
key = os.environ.get('ENCRYPTION_KEY')
f = Fernet(key)
return f.encrypt(json.dumps(data).encode())
test cases passed, vs 14 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.