service-check

Solid

Use to evaluate a service or feature against Downe's 15 principles of good services.

AI & Automation 41 stars 3 forks Updated today MIT

Install

View on GitHub

Quality Score: 86/100

Stars 20%
54
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Service Check Skill Evaluate against Lou Downe's 15 principles. ## Checklist For each principle, assess: Pass / Partial / Fail / N/A 1. **Easy to find**: Can users find this service without knowing its name? - [ ] Discoverable through natural search terms - [ ] Linked from logical starting points 2. **Clearly explains its purpose**: Is it immediately clear what this does? - [ ] Purpose statement visible without scrolling - [ ] Target audience identifiable 3. **Sets expectations**: Do users know what will happen? - [ ] Timeline/process visible upfront - [ ] Requirements stated before starting 4. **Enables completion**: Can users finish what they came to do? - [ ] End-to-end journey works - [ ] No organizational barriers blocking completion 5. **Familiar**: Does it work the way users expect? - [ ] Uses conventions users know - [ ] No surprising behavior 6. **No prior knowledge needed**: Can a new user succeed? - [ ] No jargon or acronyms without explanation - [ ] No assumed context 7. **Agnostic of org structures**: Are internal boundaries invisible? - [ ] Users don't need to know which department handles what - [ ] No internal handoffs visible to users 8. **Minimum steps**: Is every step necessary? - [ ] No redundant data entry - [ ] No unnecessary confirmation steps 9. **Consistent**: Is language/design uniform throughout? - [ ] Same terms used for same concepts - [ ] Visual patterns consistent 10. **No dead...

Details

Author
haabe
Repository
haabe/mycelium
Created
3 months ago
Last Updated
today
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

privacy-check

Use to assess Privacy by Design compliance and GDPR/data protection alignment for a feature or system.

41 Updated today
haabe
AI & Automation Listed

values-check

Pressure-tests a decision, plan, or piece of client-facing work against Clear Measure's core values before you commit to it. Use before finalizing a client proposal, staffing decision, or scope change, when a decision "feels off," or when onboarding a new hire to how decisions get made.

0 Updated today
ClearMeasureLabs
AI & Automation Listed

bs-check

Use before telling a client or stakeholder "this is fixed", before deploying changes to a production site or service, before activating or modifying a live automation/workflow, before claiming an integration works end-to-end, before quoting pricing or API behavior in a comparison, or before running a destructive infrastructure command. Also use when the user says "confidence check", "how confident are you", "validate this", "pressure-test this", "/bs-check", or whenever a confident-sounding claim has not been directly validated by a query, observation, comparison, or quotable source. ALSO covers design-time reasoning audits via subcommands - "bs-check premise" (are we solving the right problem? premise acceptance - Socratic + Steelman), "bs-check approach" (did we commit too fast? - Burden of Proof, Cold Start, Alternatives, Pre-mortem), "bs-check fresh" (all 9 patterns, fresh-context sub-agent). Trigger phrases for those - challenge this, push back, devil's advocate, poke holes, steelman this, are we solving

0 Updated today
GemSpecter