persona-researcher
Organize research — manage references, notes, and collaboration.
Install with Tessl CLI
npx tessl i github:googleworkspace/cli --skill persona-researcher54
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
32%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 description is too brief and vague to effectively guide skill selection. It lacks specific concrete actions, misses common user terminology for research management, and critically omits any 'Use when...' guidance. The description would benefit significantly from explicit triggers and more detailed capability listing.
Suggestions
Add a 'Use when...' clause with trigger terms like 'citations', 'bibliography', 'sources', 'papers', 'literature review', 'Zotero', 'Mendeley'
Expand specific actions to include concrete capabilities like 'create citations in APA/MLA format', 'organize source materials', 'generate bibliographies', 'annotate papers'
Clarify the niche by specifying whether this is for academic research, market research, or general research to reduce conflict with other skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (research) and some actions (manage references, notes, collaboration), but these are fairly high-level and not comprehensive. Doesn't specify concrete actions like 'create citations', 'export bibliography', or 'tag sources'. | 2 / 3 |
Completeness | Describes what it does at a high level but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per rubric guidelines, missing explicit trigger guidance caps this at 2, but the 'what' is also weak, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes some relevant keywords ('research', 'references', 'notes', 'collaboration') but misses common variations users might say like 'citations', 'bibliography', 'sources', 'papers', 'literature review', or 'annotate'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Research' and 'notes' are fairly generic terms that could overlap with note-taking skills, documentation skills, or general organization tools. 'References' provides some specificity toward academic/citation management but isn't definitive. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
60%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is concise and well-organized but lacks actionability and workflow clarity. It reads more like a feature list than executable guidance—telling Claude what tools exist without showing how to use them in practice or how steps connect in a research workflow.
Suggestions
Add at least one concrete example showing a complete research workflow (e.g., 'To log a new paper: 1. Upload with `gws drive files upload paper.pdf --folder research/`, 2. Create notes with `gws docs +write`...')
Provide executable command examples with actual parameters rather than just referencing command names
Sequence the instructions into a coherent workflow with clear steps for common research tasks like 'adding a new paper' or 'sharing findings'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, avoiding unnecessary explanations. It assumes Claude knows what research organization entails and jumps directly to actionable commands and workflows. | 3 / 3 |
Actionability | Provides specific command references (e.g., `gws docs +write`, `gws sheets +append`) but lacks concrete examples of actual usage, input/output, or copy-paste ready commands. The guidance is directional rather than executable. | 2 / 3 |
Workflow Clarity | Instructions are listed as independent bullet points without clear sequencing or workflow structure. There's no validation, checkpoints, or guidance on how these steps connect in a research workflow. | 1 / 3 |
Progressive Disclosure | Appropriately structured with clear prerequisite skills referenced, relevant workflows linked, and tips separated. For a simple coordination skill, the organization is clean and navigable. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 Passed | |
- 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.