safety-quotient-lab
Official@safety-quotient-lab · Global
Measuring and protecting human dignity through applied psychology, AI analysis, and open-source tools
Agent Skills by safety-quotient-lab
Showing 9 vetted skills indexed across 1 GitHub repositories.
scan-peer
Scan peer repository content for compliance and quality issues.
iterate
Orchestrate an autonomous work loop that synchronizes, prioritizes, and executes tasks.
hunt
Scan project documents and prioritize next work items by value and effort.
cycle
Update project markdown files and commit changes to Git.
diagnose
Run systemic self-diagnostics across subsystems using SQL queries and bash scripts.
retrospect
Scan lab-notebook, journal, ideas, git log, and TODO.md files to generate retrospective reports.
doc
Persist mid-work decisions, findings, and reasoning to project documentation files.
sync
Scan transport sessions for new messages and synchronize peer agent repositories.
knock
Trace cascading effects of a decision across ten orders of impact analysis.
Frequently Asked Questions About safety-quotient-lab
FAQPage SchemaWhat specific tasks does safety-quotient-lab enable for repository management?▼
The organization enables automated repository scanning for compliance, systemic self-diagnostics via database queries, and the synchronization of peer messaging sessions. It facilitates the tracking of cascading decision impacts and the generation of retrospective reports based on project documentation and version control history.
Which personas benefit most from these diagnostic capabilities?▼
Compliance officers, technical auditors, and project leads benefit from these capabilities. These personas use the provided functions to maintain documentation integrity, ensure repository quality standards, and perform deep-impact analysis on complex decision-making processes within technical environments.
What are the primary dependencies for running these diagnostic functions?▼
These functions require a standard Git environment and access to project-specific markdown files, lab-notebooks, and SQL-compatible databases. Users must ensure their local repository structure includes standard documentation files like TODO.md and git logs to enable full diagnostic and retrospective reporting features.