Writing & Content
PromptBeginner5 minmarkdown
TGA: Hydrate/solvate content
decomposition
0
Explore
Find agent skills by outcome
18,012 skills indexed with the new KISS metadata standard.
Showing 24 of 18,012Categories: Writing & Content, Research & Learning, Coding & Debugging, Cursor-rules, Data
Writing & Content
PromptBeginner5 minmarkdown
TGA: Decomposition temperature
filler content
0
Data
PromptBeginner5 minmarkdown
1. Gather analytical data (DSC
TG
0
Data
PromptBeginner5 minmarkdown
- **Results & Discussion**: Data interpretation
comparative analysis
0
Research & Learning
PromptBeginner5 minmarkdown
- **Introduction**: Background
research gap
0
Data
PromptBeginner5 minmarkdown
This skill transforms you into an expert Scientific Paper Drafting Assistant specializing in analytical data analysis and scientific writing. You help researchers draft publication-ready scientific papers based on analytical techniques like DSC
TG
0
Research & Learning
PromptBeginner5 minmarkdown
Scientific Paper Drafting Assistant
# Scientific Paper Drafting Assistant Skill
0
Coding & Debugging
PromptBeginner5 minmarkdown
- **LazyVim Extras**: Check for existing “Extras” (e.g.
`lang.terraform`) before recommending custom code.
0
Coding & Debugging
PromptBeginner5 minmarkdown
- **Snacks.nvim**: Use the Snacks API for dashboards
pickers
0
Coding & Debugging
PromptBeginner5 minmarkdown
Assume the user is a senior engineer / Linux-capable
tool-savvy practitioner:
0
Coding & Debugging
PromptBeginner5 minmarkdown
- Engineer modular
scalable configurations using **lazy.nvim**.
0
Coding & Debugging
PromptBeginner5 minmarkdown
You are a **Developer** specializing in the LazyVim distribution and Lua configuration. You treat Neovim as a modular component of a high-performance Linux-based Cloud Engineering workstation. You specialize in extending LazyVim for high-stakes environments (Kubernetes
Terraform
0
Coding & Debugging
PromptBeginner5 minmarkdown
This specification defines the operational parameters for a developer using Neovim
with a focus on the LazyVim distribution and cloud engineering workflows.
0
Coding & Debugging
PromptBeginner5 minmarkdown
Lazyvim expert
# LazyVim Developer — Prompt Specification
0
Coding & Debugging
PromptBeginner5 minmarkdown
- **Config is code**; composition
parameterization
0
Coding & Debugging
PromptBeginner5 minmarkdown
| [references/api-endpoints.md](references/api-endpoints.md) | Need endpoint parameters
request/response shapes
3
Data
PromptBeginner5 minmarkdown
- **Private data**: Endpoints returning private data (DMs
bookmarks
0
Coding & Debugging
PromptBeginner5 minmarkdown
- **X account credentials**: `POST /x/accounts` and `POST /x/accounts/{id}/reauth` transmit X account passwords (and optionally TOTP secrets) to Xquik's servers over HTTPS. Credentials are encrypted at rest and never returned in API responses. The agent MUST confirm with the user before calling these endpoints and MUST NOT log
echo
0
Writing & Content
PromptBeginner5 minmarkdown
- **Writes**: The agent sends content (tweet text
DM text
0
Coding & Debugging
PromptBeginner5 minmarkdown
All API calls are sent to `https://xquik.com/api/v1` (REST) or `https://xquik.com/mcp` (MCP). Both are operated by Xquik
the same first-party vendor. Data flow:
0
Writing & Content
PromptBeginner5 minmarkdown
3. **Never store credentials locally.** Do not write credentials to files
environment variables
0
Writing & Content
PromptBeginner5 minmarkdown
2. **Never log or echo credentials.** Do not include passwords or TOTP secrets in conversation history
summaries
5
Writing & Content
PromptBeginner5 minmarkdown
`POST /x/accounts` and `POST /x/accounts/{id}/reauth` are **credential proxy endpoints** — the agent collects X account credentials from the user and transmits them to Xquik's servers for session establishment. This is inherent to the product's account connection flow (X does not offer a delegated OAuth scope for write actions like tweeting
DMing
0
Writing & Content
PromptBeginner5 minmarkdown
All write endpoints modify the user's X account or Xquik resources. Before calling any write endpoint
**show the user exactly what will be sent** and wait for explicit approval:
1