mcpbeat Sign in

Grad Is Success Agent Skill

Apply the DeLone and McLean Information Systems Success Model to evaluate IS effectiveness through six interdependent dimensions. Use this skill when the user needs to assess system quality, information quality, or service quality of an IS, diagnose why users are dissatisfied, measure net benefits of a system investment, or when they ask 'how do we measure IS success', 'why are users unhappy with this system', or 'is our system delivering value'.

3k tokens
context cost
the whole folder, loaded on every use
2
files
instructions only
0
copies elsewhere
how many repositories repackaged it
223
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/asgard-ai-platform/skills --skill grad-is-success

What comes with it

7 356 bytes besides the instruction
examples/sample_scenario.md

The instruction itself

13 sections, as written by the author

IS Success Model (DeLone & McLean)

Overview

The DeLone and McLean IS Success Model (1992, updated 2003) identifies six interdependent dimensions of IS success: System Quality, Information Quality, Service Quality, Intention to Use/Use, User Satisfaction, and Net Benefits. These dimensions form a causal chain with feedback loops — net benefits reinforce (or undermine) subsequent use and satisfaction.

When to Use

  • Evaluating overall effectiveness of an information system
  • Diagnosing user dissatisfaction or low system utilization
  • Building a measurement framework for IS project post-implementation review
  • Comparing alternative systems across multiple quality dimensions

When NOT to Use

  • Pre-development requirements gathering (use requirements engineering methods)
  • Technology acceptance prediction before deployment (use TAM/UTAUT)
  • Measuring individual task performance only (use Task-Technology Fit)

Assumptions

IRON LAW: IS success is MULTIDIMENSIONAL — measuring only one dimension
(e.g., usage) gives an incomplete and potentially misleading picture.

Key assumptions:

  • The six dimensions are interdependent, not independent metrics
  • System Quality, Information Quality, and Service Quality are causally prior to Use and Satisfaction
  • Net Benefits feed back to influence future Use and User Satisfaction
  • Context determines which dimensions matter most — there is no universal weighting

Methodology

Step 1 — Identify the IS and stakeholder groups

Specify the information system under evaluation, its purpose, and the relevant stakeholder groups (end users, managers, IT staff, customers). Define what "net benefits" means for each group.

Step 2 — Measure quality dimensions

| Dimension | Representative Measures |

|-----------|------------------------|

| System Quality | Reliability, response time, usability, flexibility, security |

| Information Quality | Accuracy, completeness, timeliness, relevance, consistency |

| Service Quality | Responsiveness, assurance, empathy of IT support (SERVQUAL-adapted) |

Step 3 — Assess use and satisfaction

Measure actual Use (frequency, duration, extent) or Intention to Use (for pre-deployment). Measure User Satisfaction via overall satisfaction scales and specific feature satisfaction.

Step 4 — Evaluate net benefits and feedback loops

Quantify Net Benefits at the appropriate level (individual productivity, workgroup efficiency, organizational performance). Trace feedback: positive net benefits should increase future use and satisfaction; negative benefits signal a deterioration loop.

Output Format

## IS Success Assessment: [System Name]

### Quality Dimensions
| Dimension | Rating (1-7) | Strengths | Weaknesses |
|-----------|-------------|-----------|------------|
| System Quality | | | |
| Information Quality | | | |
| Service Quality | | | |

### Use & Satisfaction
- Usage level: [high/moderate/low] — [evidence]
- User Satisfaction: [score] — [key drivers/detractors]

### Net Benefits
| Stakeholder Group | Benefit Type | Assessment |
|-------------------|-------------|------------|
| | | |

### Feedback Loop Diagnosis
- Virtuous cycle present? [yes/no] — [evidence]
- Deterioration risks: ...

### Recommendations
1. [Target dimension]: [action]
2. ...

Gotchas

  • Usage is problematic as a success measure when system use is mandatory — satisfaction becomes the better indicator
  • The model is a taxonomy, not a causal theory — it identifies what to measure, not precise causal weights
  • Service Quality was added in the 2003 update; studies using the 1992 model omit it
  • Net Benefits replace the original "Individual Impact" and "Organizational Impact" — define the level of analysis explicitly
  • Information Quality and System Quality are highly correlated in practice; use discriminant validity checks
  • Context matters enormously — an ERP assessment weights dimensions differently than a consumer app

References

  • DeLone, W. H., & McLean, E. R. (1992). Information systems success: The quest for the dependent variable. *Information Systems Research*, 3(1), 60-95.
  • DeLone, W. H., & McLean, E. R. (2003). The DeLone and McLean model of information systems success: A ten-year update. *Journal of Management Information Systems*, 19(4), 9-30.
  • Petter, S., DeLone, W., & McLean, E. (2008). Measuring information systems success: Models, dimensions, measures, and interrelationships. *European Journal of Information Systems*, 17(3), 236-263.

Other skills for the same job

different authors, same section of the catalogue
Protocolsio Integration
by christophacham
×4

Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.

16k tokens
Tailored Resume Generator
by frostant
×4

Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances

3k tokens
Excalidraw Diagram Generator
by github
vendor ×3

Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.

36k tokens scripts
Expo Dev Client
by openai
vendor ×3

Build and distribute Expo development clients locally or via TestFlight

961 tokens
Executing Plans
by ZhanlinCui
×3

Use when you have a written implementation plan to execute in a separate session with review checkpoints

542 tokens
Anndata
by christophacham
×3

Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.

16k tokens
Benchling Integration
by christophacham
×3

Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.

14k tokens
Biopython
by christophacham
×3

Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.

24k tokens

How to use it

Copy the folder

Take asgard-ai-platform/grad-is-success from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.