research-technology

Researches a technology's capabilities, limits, costs, failure modes, and licence terms from primary sources.

1|Updated Jun 30, 2026
One-click install
npx skills add https://github.com/Lia-Creative/lia-plugins --skill research-technology-lia-creative
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: research-technology
Source: https://github.com/Lia-Creative/lia-plugins/tree/main/lia-tools/skills/research-technology
Command: npx skills add https://github.com/Lia-Creative/lia-plugins --skill research-technology-lia-creative

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Evaluating a technology from marketing pages and READMEs produces decisions built on claims rather than evidence. This Skill structures the technology domain of a research plan so every finding comes from primary documentation, issue trackers, incident history, and verbatim licence text. ## Core Features & Use Cases - Evidence-based capability review: Documents what a technology actually does and explicitly does not do, at a named version, with dated limits and quotas. - Cost, failure, and licence analysis: Identifies the pricing dimension that drives the bill, published failure modes with recovery paths, and quotes licence and data terms verbatim. - Use Case: Before adopting a managed queue service, dispatch this Skill to return its rate limits at the current version, its incident history, the cost driver at your message volume, and the exact data-residency terms — filed as a research corpus entry. ## Quick Start Ask the agent to research the technology domain for a specific technology you are evaluating, naming the version and your expected usage shape.

Frequently Asked Questions about research-technology

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I research a technology before adopting it?▼

Start with primary documentation at the exact version you would use, then read the issue tracker and incident history rather than the README. Record limits with versions and dates, quote licence terms verbatim, and note who has run it at a comparable scale.

What sources count as valid evidence in technology research?▼

Valid sources include official documentation at a named version, the licence text itself, public issue trackers, incident and status history, benchmarks that state their method, dated practitioner reports at comparable scale, and your own reproducible measurements.

Does this Skill decide which technology to choose?▼

No. It produces evidence about a specific technology — capabilities, limits, costs, and risks — but never the choice itself. Architecture and solution-pattern seats make the decision using the findings this domain returns.

Can this Skill build a proof of concept to test a technology?▼

No. Building a proof of concept is separate build work on its own ticket. This Skill can recommend that a spike is needed and state exactly what question it would settle.

How are licence and data terms handled in the research output?▼

Licence, data residency, retention, and cost terms are quoted verbatim with their locator, never paraphrased. Anything with an owner is asked directly rather than inferred.