creating-github-issues-from-web-research
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill creating-github-issues-from-web-researchThis skill enhances Claude's ability to conduct web research and translate findings into actionable GitHub issues. It automates the process of extracting key information from web search results and formatting it into a well-structured issue, ready for team action. Use this skill when you need to research a topic and create a corresponding GitHub issue for tracking, collaboration, and task management. Trigger this skill by requesting Claude to "research [topic] and create a ticket" or "find [information] and generate a GitHub issue".
Validation
81%| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
Total | 13 / 16 Passed | |
Implementation
20%This skill content reads like marketing documentation rather than actionable instructions for Claude. It describes what the skill does conceptually but provides no concrete implementation details, code examples, API calls, or issue templates. The content assumes Claude needs to be told what web search and GitHub issues are, wasting tokens on explanations rather than providing executable guidance.
Suggestions
Replace the abstract 'How It Works' section with concrete code or commands showing how to format search queries and structure the GitHub API call for issue creation
Add a concrete issue template showing the exact markdown structure Claude should use when creating issues (title format, body sections, label syntax)
Include specific examples of the actual issue content that would be generated, not just descriptions of what the issue 'will contain'
Add validation steps: how to verify the issue was created successfully, how to handle API errors, and what to do if search results are insufficient
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and explains concepts Claude already knows (what web search is, what GitHub issues are, how extraction works). The 'How It Works' section describes obvious steps rather than providing actionable guidance. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance provided. The content describes what 'the skill will do' abstractly rather than instructing Claude how to do it. No API calls, no issue templates, no actual implementation details. | 1 / 3 |
Workflow Clarity | Steps are listed in a sequence (search, extract, create), but there are no validation checkpoints, no error handling, and no concrete details about what constitutes successful completion or how to handle failures. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but everything is inline in one file. The 'Integration' section mentions other skills but provides no links or references. No external documentation is referenced for advanced usage. | 2 / 3 |
Total | 6 / 12 Passed |
Activation
82%This description does well at explaining when to use the skill with explicit trigger phrases and clear use cases. However, it lacks specificity about the concrete actions performed (what information is extracted, what issue fields are populated) and uses some filler language ('enhances Claude's ability', 'automates the process') that could be replaced with more concrete details.
Suggestions
Replace vague phrases like 'extracting key information' and 'well-structured issue' with specific actions (e.g., 'populates title, description, labels, and acceptance criteria from research findings')
Remove filler language like 'enhances Claude's ability' and 'automates the process' - start directly with what the skill does
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (web research + GitHub issues) and describes actions like 'extracting key information' and 'formatting into well-structured issue', but lacks specific concrete actions like what fields are populated, what research sources are used, or what 'well-structured' means. | 2 / 3 |
Completeness | Clearly answers both what ('conduct web research and translate findings into actionable GitHub issues') and when ('Use this skill when you need to research a topic and create a corresponding GitHub issue') with explicit trigger examples provided. | 3 / 3 |
Trigger Term Quality | Includes good natural trigger terms: 'research [topic] and create a ticket', 'find [information] and generate a GitHub issue', plus keywords like 'GitHub issues', 'tracking', 'collaboration', 'task management' that users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of web research + GitHub issue creation is somewhat specific, but could overlap with general GitHub skills or general research skills. The 'research and create ticket' trigger helps but 'task management' and 'collaboration' are generic terms. | 2 / 3 |
Total | 10 / 12 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.