> For the complete documentation index, see [llms.txt](https://enercalc.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://enercalc.com/docs/e3d-user-manual/interface/toc175916526/input-data/toc161393902.md).

# Shells

How to enter and edit shell elements in a spreadsheet using Tables Shells.

Tables > Shells prompts you with the following dialog.

![](https://560001759-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWNe8U6EBBBdUJHdb2X9G%2Fuploads%2Fgit-blob-2679b197ea32432c63ff15c4558a4fe814df7067%2FFASTFR~1_img148.png?alt=media)

It allows you to enter shells in a spreadsheet. Each shell includes the IDs of four element nodes, the material and thickness IDs, the element local angle, and selection status. You may not modify the shell IDs. All other IDs must be valid (defined). Material and thickness combo boxes are provided for you to correctly pick and apply proper material and thickness IDs to selected shells.

An empty row is allowed if all rows below it are empty (except the shell ID and status fields). You may not delete the existing shells in this dialog. To delete the existing shells, you must dismiss this dialog and click Modify > Delete.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://enercalc.com/docs/e3d-user-manual/interface/toc175916526/input-data/toc161393902.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
