> For the complete documentation index, see [llms.txt](https://nfts-101.kyzzen.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nfts-101.kyzzen.io/evaluating-nft-projects/key-factors/overall-framework.md).

# Overall Framework

Here we share a potential general framework that we can use for evaluating NFT projects, which is a neat summary of the aforementioned points.

<figure><img src="/files/jgihZKrbxiIcloiMxile" alt=""><figcaption><p>A General Framework for Evaluating NFT Projects</p></figcaption></figure>

Typically, projects that score higher across the board tend to generally be higher quality than those that don’t, but there is certainly no one-size-fits-all approach to evaluating all NFT projects the same way.&#x20;

For instance, a project that focuses mostly on high quality, original artwork may rank poorly on utility/roadmap, but if the artist is widely known for their great, original art, and there is a solid marketing strategy and active community development, it can still be considered investment-worthy. Similarly, a project that focuses on pure utility with revenue-sharing/staking/tokens could perhaps get away with lower quality art but has a strong team capable of building great utility. It usually depends on what the key value propositions of the project being evaluated are.

That being said, projects that are positioned to be much larger-scale in nature than the average NFT project (e.g. metaverses) should be expected to score better across all categories (i.e. Team, Artwork, Utility/Roadmap, Marketing Strategy, Community Development).&#x20;


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://nfts-101.kyzzen.io/evaluating-nft-projects/key-factors/overall-framework.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.