mobile-design
Mobile-first design thinking and decision-making for iOS and Android apps. Touch interaction, performance patterns, platform conventions. Teaches principles, not fixed values. Use when building React Native, Flutter, or native mobile apps.
89
87%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid skill description with excellent trigger terms and completeness. The main weakness is the specificity of capabilities - it describes categories of knowledge (touch interaction, performance patterns) rather than concrete actions the skill enables. The explicit 'Use when...' clause and platform-specific terminology make it highly functional for skill selection.
Suggestions
Replace abstract categories with concrete actions, e.g., 'Guides touch target sizing, gesture implementation, platform-specific navigation patterns, and mobile performance optimization'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (mobile design) and mentions some concepts like 'touch interaction, performance patterns, platform conventions' but these are categories rather than concrete actions. Lacks specific verbs describing what the skill actually does (e.g., 'optimizes touch targets', 'implements platform-specific navigation'). | 2 / 3 |
Completeness | Clearly answers both what ('Mobile-first design thinking, touch interaction, performance patterns, platform conventions, teaches principles') and when ('Use when building React Native, Flutter, or native mobile apps') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'iOS', 'Android', 'React Native', 'Flutter', 'mobile apps', 'mobile-first'. These are terms developers naturally use when discussing mobile development. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on mobile app development with distinct platform mentions (iOS, Android, React Native, Flutter). The 'mobile-first' and specific framework mentions make it unlikely to conflict with general web design or other UI skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured mobile design skill with excellent actionability through concrete code examples, specific values, and comprehensive anti-pattern tables. The progressive disclosure is exemplary with clear file references and when-to-read guidance. The main weakness is moderate verbosity with some redundant emphasis and repeated content that could be consolidated.
Suggestions
Consolidate the anti-patterns section - the detailed tables and the 'AI MOBILE ANTI-PATTERNS' section have overlapping content that could be merged
Remove redundant 'read the files' emphasis - the point is made clearly once; repeating it multiple times adds tokens without value
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy (anti-patterns listed twice in different formats, repeated emphasis on reading files). The tables and quick references are efficient, but the overall length could be tightened without losing value. | 2 / 3 |
Actionability | Provides fully executable code examples for both React Native and Flutter, specific pixel values for touch targets, concrete commands for scripts, and copy-paste ready patterns. The anti-pattern tables with direct alternatives are highly actionable. | 3 / 3 |
Workflow Clarity | Clear sequencing with mandatory checkpoints, pre-development checklists, per-screen checklists, and release checklists. The checkpoint template with explicit validation (can't fill it = go back and read) provides excellent feedback loops. | 3 / 3 |
Progressive Disclosure | Excellent structure with quick reference summaries inline and clear one-level-deep references to detailed files (touch-psychology.md, mobile-performance.md, etc.). Tables clearly indicate which files to read and when, with good navigation signals. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 11 Passed | |
- Repository
- lchenrique/politron-ide
- Commit
7114206
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.