Paragraph Counter
text.count_paragraphs
Overview
You pass text (or a file_ref); we split it on runs of blank lines, drop the empty blocks, and return how many paragraphs are left — plus the paragraph text itself when you ask for segments. You choose whether each block is trimmed. Do not use this for line, sentence, or word counting; the count skills for those units are separate.
Paragraph boundaries depend on formatting conventions. We make the rule explicit so you get auditable counts instead of guesswork.
Reliability
VERIFIABLE and deterministic — identical text, policy, and trim_paragraphs setting always yield the same count. Input validation (not retryable): invalid policy; missing text and file_ref.
Context footprint
One call replaces fragile regex-based paragraph splitting. Accepts inline text up to 1,000,000 chars or file_ref (up to 2 MB). Upload files via POST /v1/files/upload before passing file_ref. A successful call costs 1 execution credit.
When to use it
When you need to quantify document structure and want the separation policy documented in the response.
Do not use when you need semantic paragraph understanding — that requires NLP tooling, not separator rules.
Scope
Non-goals
- Does not perform semantic paragraph detection
- Does not treat Markdown headings or HTML tags as paragraph breaks
Properties
Capabilities
Cost & billing
Flat rate per invocation
File handling
File limits
Constraints this skill applies to your input and generated files. The “Limited by” column shows the static source of each cap; none of these can be raised by upgrading your plan.
| Limit | Value | Limited by |
|---|---|---|
| Maximum size per input file | 1.9 MiB | Skill maximum |
How we handle your data
What this means
This skill may receive sensitive content, but it does not target sensitive data and returns only a structured non-sensitive result.
Squillify guarantees
- Runs inside Squillify
- This skill runs inside Squillify.
- Payloads are not sent to an external service by this skill.
- Squillify does not permanently store submitted payloads.
- Telemetry records metadata only, not submitted content.
- Submitted payloads are not used for training.
- Submitted payloads are not reviewed by humans.
- This skill does not target sensitive data.
- The response does not contain submitted content.
Your responsibility
Squillify does not determine whether submitted content is sensitive. Your application is responsible for deciding what data it is allowed to submit. Your application is responsible for securing the response.
Input schema
| Field | Type | Required | Description |
|---|---|---|---|
| text | string | No | Bounded inline text source. Required unless file_ref is provided. |
| file_ref | string | No | Tenant-scoped opaque text-file reference. Omit it to use the required inline text; never send both. |
| policy | string | No | Separator policy; omit it for blank_line_separated. |
| trim_paragraphs | boolean | No | Whether paragraph edges are trimmed; omit it for true. |
| return_segments | boolean | No | Whether paragraph text is returned; omit it for false. |
Output schema
| Field | Type | Required | Description |
|---|---|---|---|
| skill | string | Yes | Producing skill key. |
| count | integer | Yes | Counted paragraphs. This non-negative total is bounded by the documented input limit. |
| unit | string | Yes | Measurement unit for the returned paragraph total. |
| policy | string | Yes | Applied paragraph policy. |
| segments | array | No | Returned paragraphs in document order. The item shape is one bounded string and the array contains from 0 through 1000000 items. |
| warnings | array | Yes | Bounded warning array containing from 0 through 4 items, where each item is one non-fatal advisory string. |
API contract
POST /v1/executecurl -sS -X POST "$BASE/v1/execute" -H "Authorization: Bearer $KEY" -H 'Content-Type: application/json' -d '{"skillKey":"text.count_paragraphs","input":{"text":"Para one.\n\nPara two.","policy":"blank_line_separated"}}'import { Squillify } from "@squillify/sdk";
const sq = new Squillify({ apiKey: process.env.SQUILLIFY_API_KEY });
const { output } = await sq.execute("text.count_paragraphs", {"policy":"blank_line_separated","text":"Para 1\n\nPara 2"});Errors
| Code | HTTP | Retryable | Description |
|---|---|---|---|
| VALIDATION_ERROR | 400 | No | The request payload failed schema validation. |
| UNAUTHORIZED | 401 | No | Missing or invalid API key. |
| SKILL_NOT_ACCESSIBLE | 403 | No | The API key is not granted access to this skill. |
| SKILL_NOT_AVAILABLE_FOR_PLAN | 403 | No | This skill is not included in your current plan. |
| PLAN_ELIGIBILITY_UNAVAILABLE | 503 | Yes | Plan eligibility could not be decided. Retry after backoff. |
| SKILL_NOT_FOUND | 404 | No | The requested skill or version does not exist. |
| TENANT_RATE_LIMITED | 429 | Yes | Request rate limit exceeded. Retry after backoff. |
| QUOTA_EXCEEDED | 429 | Yes | Plan quota exhausted. Retryable once the quota period resets. |
| EXECUTION_TIMEOUT | 504 | Yes | Execution exceeded the allowed time budget. |
Other limits
| Limit | Value |
|---|---|
| Recommended inline bytes | 32 KiB |
Limitations
- Does not perform semantic paragraph detection
- Does not treat Markdown headings or HTML tags as paragraph breaks
- Semantic paragraph detection that requires NLP
- Structure analysis where headings or list items define logical sections
How to call
POST /v1/execute (requires authentication)
{
"skillKey": "text.count_paragraphs",
"input": {
"policy": "blank_line_separated",
"text": "Para 1\n\nPara 2"
}
}Examples
Blank-line separated paragraphs
{
"policy": "blank_line_separated",
"text": "Para 1\n\nPara 2"
}{
"warnings": [],
"unit": "paragraph",
"policy": "blank_line_separated",
"skill": "text.count_paragraphs",
"count": 2
}Single block without blank lines
{
"policy": "non_empty_line_blocks",
"text": "Line one\nLine two\nLine three"
}{
"warnings": [],
"unit": "paragraph",
"policy": "non_empty_line_blocks",
"skill": "text.count_paragraphs",
"count": 1
}Recommended use cases
- Measure document structure before summarization or chunking
- Validate that content meets paragraph-count guidelines
- Report formatting metrics alongside word or sentence counts
Avoid for
- Semantic paragraph detection that requires NLP
- Structure analysis where headings or list items define logical sections
Related skills
Composable with
Safety & privacy
- Runs without calling any external service.
- Your payloads are never stored permanently.
- Telemetry captures metadata only — never your payload contents.
- We never train models on your payloads.
- No human reviews your payloads.