mrmps
UserSix opinionated agent skills for thinking, simplifying, writing, and shipping.
Categories
Indexed Skills (5)
office-hours
YC-style office hours. Two modes. Startup mode runs six forcing questions that expose demand reality, status quo, desperate specificity, the narrowest wedge, what you learned from watching users, and future-fit. Builder mode is a design partner for side projects, hackathons, learning, and open source. Ends with a design doc and one concrete assignment. Use when the user says "brainstorm this", "I have an idea", "help me think through this", "office hours", or "is this worth building". Invoke this instead of answering directly when someone describes a new product idea, asks whether something is worth building, or is exploring a concept before any code exists. Run before plan-ceo-review.
plan-ceo-review
CEO/founder-mode plan review. Rethink the problem, find the 10-star product, challenge premises, and expand scope when expansion creates a better product. Four modes: SCOPE EXPANSION (dream big), SELECTIVE EXPANSION (hold scope and cherry-pick), HOLD SCOPE (maximum rigor), SCOPE REDUCTION (strip to essentials). Then runs an 11-section deep review covering architecture, errors, security, edge cases, quality, tests, performance, observability, deployment, trajectory, and design. Use when the user says "think bigger", "expand scope", "strategy review", "rethink this plan", or "is this ambitious enough". Suggest it when someone is questioning the scope or ambition of a plan. Runs well after office-hours.
gr
Run a complete Greptile CLI review, merge, and production deployment loop for the current pull request: inspect findings, fix every actionable issue, verify changes, re-review until clean, push, wait for every check, merge only when none are failed or pending, deploy through the repository's documented production path, and verify production. Use when the user invokes /gr or asks to run Greptile, address its review, merge a PR, and ship it.
meaningful-contribution
Require software changes to be demonstrated, not merely generated. Use when implementing, fixing, refactoring, reviewing, or preparing a pull request for code, configuration, migrations, build tooling, or other behavior-affecting repository changes—especially agent-generated changes that need manual verification, automated regression coverage, edge-case testing, honest naming and types, and concise evidence for reviewers.
unsummarizable
Make prose dense with ideas and resistant to loss through summarization. Use when drafting or revising essays, memos, documentation, explanations, posts, or other nonfiction that should contain no fluff, repetition, or disposable framing.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.